Python: dict .get() calls misidentified as Route nodes

[RyanKim17920]

Bug

dict.get("key") calls inside function bodies are parsed as Route nodes, inflating route counts with false positives.

Example

user_id = payload.get("sub")       # → creates Route node "GET sub"
username = payload.get("username") # → creates Route node "GET username"

These appear in search_graph(label="Route") results alongside real FastAPI routes.

Impact

Running get_architecture(aspects=["routes"]) or querying Route nodes returns ~125 spurious nodes mixed with real endpoints, making route discovery unreliable without manual filtering.

Workaround

Filter by WHERE qualified_name =~ '.*routers.*' to restrict to actual router files.

Suggested Fix

Route detection should require the .get() call to be on an APIRouter or FastAPI instance (i.e. the receiver is typed as or assigned from APIRouter()), not arbitrary dict variables.

[kingchenc]

This might be a relatively straightforward fix.

The goRouteRe regex in internal/httplink/httplink.go matches .Get("..."), .Post("...") etc. without checking what the receiver object is. In Python files this causes dict.get("key"), payload.get("sub") and similar dictionary method calls to be matched as HTTP route definitions.

Express already has a solution for this exact problem with the expressReceiverAllowlist that restricts matching to known router variable names like app, router etc.

The same approach could be applied here: either skip goRouteRe entirely for .py files, or add a receiver validation that checks whether the object calling .get() is actually a router instance and not a regular dictionary or other data structure.

Looking at the code, the expressReceiverAllowlist pattern at the bottom of httplink.go already shows how this filtering works.

Applying a similar allowlist or file extension guard to goRouteRe could eliminate the false positives. No guarantee this is the full picture since there might be edge cases I am not seeing, but the root cause seems clear.

[kingchenc]

Fixed in PR #66.

Root cause: extractKtorRoutes() and extractGoRoutes() ran on all files including Python. The Ktor regex \b(get|post|...)\("..." matched payload.get("sub") creating false Route nodes.

Fix: Added file extension guard in discoverRoutes() — each source-based route extractor now only runs on its own language's files (.go, .js/.ts, .php, .kt/.kts). Verified on a real FastAPI project: 0 false positives from dict .get() calls.

[DeusData]

Fixed in 6a2b1f5 — route extractors are now scoped by file extension (.go → Go, .php → Laravel, .js/.ts → Express, .kt → Ktor). Python .get() calls no longer trigger the Ktor/Go route regex. Ported from PR #65. Thanks for reporting!