PHP/Laravel: routes inside Route::prefix()->group() produce no Route nodes

[paolo-blocklabs]

Version: 0.8.1 (linux-amd64-portable) · Language: PHP 8.4 / Laravel 12

Summary

Routes defined inside Route::prefix()->group() (the dominant pattern in production Laravel apps) produce no Route nodes. Flat definitions in the same file extract fine.

Repro

routes/api.php:

// extracts correctly → Route node __route__GET__/api/welcome
Route::get('/api/welcome', WelcomeController::class);

// produces NO Route nodes at all
Route::prefix('/users')->middleware(DomainCheckMiddleware::class)->group(function (): void {
    Route::get('/me', GetCurrentUserController::class);
    Route::post('/login', LoginUserController::class);
});

// nested prefixes also invisible
Route::prefix('companies/tenants/users')->group(function (): void { ... });

After index_repository (mode=full):

MATCH (n:Route) WHERE n.name CONTAINS 'users' RETURN n  → 0 rows

while the flat /api/welcome, /_test/* routes from the same file are present.

Impact

cross-repo-intelligence cannot match any caller to a Laravel service — in our 24-repo fleet (Go + PHP + TS) the pass returns cross_http_calls: 0 despite live FE→gateway traffic (GET /users/me). Since virtually all real Laravel apps group routes, PHP services are effectively invisible to cross-repo HTTP matching.

Same class of bug as #734 (Spring class-level @RequestMapping prefix dropped), but here the grouped routes are not merely missing their prefix — they are missing entirely.

[DeusData]

Thanks for the Laravel route-chain repro. Triage: this is a PHP route extraction bug for Route::prefix()->group() chains; I am putting it under parsing quality. This does not look covered by the v0.9.0 release, so it should stay open until we have a targeted fix and regression test.