Laravel route extraction captures ~2% of routes (13 nodes from 687 definitions)

[asemraza]

Version: 0.9.0, macOS arm64. Same Laravel 12 repo as #1211.

Observation: the project has 687 route definitions (490 in routes/web.php, 197 in routes/api.php), all using standard Laravel facade syntax - Route::get('path', [Controller::class, 'method']), route groups with prefixes/middleware, plus some closure routes. The graph contains only 13 Route nodes (~2% coverage).

Impact: for Laravel projects, Route-dependent features are effectively unavailable - cross-service route-to-call-site matching, entry-point exclusion in dead-code detection (route handlers without Route nodes risk being classified as zero-caller dead code), and route-level architecture views.

Likely gap: extraction seems not to handle the Route::VERB(...) facade patterns and/or [Controller::class, 'method'] action arrays inside Route::group blocks. Happy to provide sanitized route-file excerpts if useful.

Related context: PHP Hybrid LSP otherwise works well for us (16,870 nodes on this repo).

[asemraza]

Follow-up with stronger evidence and a working design, after deeper local investigation:

Root cause confirmed via minimal fixture: a routes file containing a plain Route::get(...) produces zero Route nodes regardless of composer.json presence, artisan file, or indexing mode. Route extraction exists for FastAPI and Phoenix, but not Laravel. The 13 Route nodes we originally reported turned out to come from HTTP call sites in tests, not from route definitions - so effective Laravel route coverage is 0%, not 2%.

Working enrichment design you may want to adopt: instead of statically parsing route files, we now use Laravel's own php artisan route:list --json as the authoritative source (it resolves groups, prefixes, middleware, and [Controller::class, 'method'] bindings correctly by definition), then insert Route nodes with HANDLES edges to the controller-method nodes, following the tool's own conventions. Result on our repo: 701 routes ingested, 660 matched to handlers (the 22 unmatched are trait/vendor-inherited handlers, expectedly). trace_path with edge_types=["HANDLES","CALLS"] then answers route-to-code questions end-to-end. Happy to share the script if useful as a reference for a built-in implementation.

Separate defect found while investigating (want a dedicated issue?): re-indexing upserts but never removes nodes for deleted files, so branch switches accumulate stale nodes - our graph carried 3,439 stale paths out of 5,508 until we purged them by checking file existence.

[DeusData]

Thanks for the detailed Laravel counts. This specific v0.9.0 extraction gap was fixed on main by commit 4ecfe4c: the current extractor recognizes facade-style Route::get/post/... registrations and composes group prefixes, with regression coverage added through #1059. Please file deleted files surviving a re-index as a separate issue because that is an incremental deletion and persistence path, not route extraction. Closing this route-extraction report as completed on main.