Route naming/caching algorithms are incompatible

[Kolyunya]

Laravel Version

11.37.0

PHP Version

8.4

Database Driver & Version

No response

Description

Problem

In my application I have multiple routes like this:

Route::apiResource('foo/translations', FooController::class);
Route::apiResource('bar/translations', BarController::class);
Route::apiResource('baz/translations', BazController::class);

All three route groups get assigned identical route names like this:

translations.index
translations.store
translations.show
translations.update
translations.destroy

That is a problem because the artisan route:cache command uses route names as cache keys and fails with the following error:

Unable to prepare route [bar/translations] for serialization.
Another route has already been assigned name [translations.index].

Proposed solution

Either route naming algorithm should use the full route URL as the route name.

Or the route caching algorithm should use the full route URL as the cache key.

Footnotes

Yes, I know that it's possible to assign route names manually for every action but that would yield an absurd amount of garbage code, manual labor, and maintenance costs.

Steps To Reproduce

Route::apiResource('foo/translations', FooController::class);
Route::apiResource('bar/translations', BarController::class);
Route::apiResource('baz/translations', BazController::class);

artisan route:cache

[crynobone]

This proposal may will create new route name for existing application and can cause breaking change. Moving this to Idea for further discussion

[Kolyunya]

Could different cache keys be used instead? That would be backward compatible.

[hans-thomas]

It can be done using names method of PendingResourceRegistration class like below:

Route::apiResource('foo/translations', FooController::class)->names('foo.translations');
Route::apiResource('bar/translations', BarController::class)->names('bar.translations');

And the route list would be like this:

[Kolyunya]

But that's quite a lot of manual labor and garbage code in the routing config that could be eliminated programmatically if we choose a different naming pattern OR use a different cache key.