Configure route list via middleware instead of config

[keasy9]

There is a problem: when changing route name in routes.php file, you need to change it in ziggy config file. And it has a solution: instead of doubling all needed routes in config, we need middleware or route facade macro-function, so it will be look like this:
Route::any('/logout', [AuthController::class, 'logout'])->name('logout')->toJs();
or
Route::any('/logout', [AuthController::class, 'logout'])->name('profile.logout')->middleware('ziggy');

I didn't go into details with this, but if this feature is welcomed, I may try to do some PR.

[bakerkretzmar]

when changing route name in routes.php file, you need to change it in ziggy config file.

What does this mean?

[keasy9]

I have to hard code the route names in both /routes/web.php and /config/ziggy.php, so if I need to change the route name, I need to change it in both files as well. It's inconvenient.

[bakerkretzmar]

Where do you need to hardcode route names in config/ziggy.php? For groups/except/only?

[keasy9]

In my case, the file looks like this:

return [
    'only' => [
        'api.*',
        'platform.main',
        'index',
        'profile.logout',
    ],
];

but that doesn't matter. The idea is to store all information about the route (including the fact that it is available in the front-end part of the application) in one place, rather than having it separated in the configuration and the route declaration.