Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
I have list of tables which are generic so I have a route with parameter:
Route::get('/tables/{table_name}', [TablesController::class, 'show_table']);
But some tables are specific so I have their routes explicitly:
Route::get('/tables/unique_table', [TablesController::class, 'show_unique_table']);
In such case, do I have to keep the routes with explicit table names above the ones with parameters? Because I know that it will lookup the first match. I just don't want to rely on the order of the routes. So maybe there is a better way to make it match so that the order won't affect anything?
do I have to keep the routes with explicit table names above the ones with parameters?
Yes, they will be matched first.
I just don't want to rely on the order of the routes.
Too bad...
So maybe there is a better way to make it match so that the order won't affect anything?
Not without some lookup table to match the explicit routes.
https://laravel.com/docs/9.x/routing#parameters-regular-expression-constraints
you may restrict a little bit first route, but this is bad idea, look into regex too
Route::get('/tables/{table_name}', [])
->whereIn('table_name', ['users', 'posts', 'products']);
Thanks, and is this situation normal? I just feel that if I reached this point where I need to rely on the order then something is wrong with my code, but might be just my feeling?
Thanks, and is this situation normal?
Yes.
I just feel that if I reached this point where I need to rely on the order then something is wrong with my code, but might be just my feeling?
This is how we ensure the Request is correctly routed - higher specificity routes first, then generic routes which catch anything not already matched (for a given URI schema)
@tykus thank you
Please or to participate in this conversation.