Requests
Architecture
Last updated
2 years ago.
how about
Route::controller('sessions', 'SessionsController');
Last updated
2 years ago.
keithwhyman said:
how about
Route::controller('sessions', 'SessionsController');
This is not "named". If I changed "sessions" to "sess" for example I would have to change every link that points to "sessions".
Last updated
2 years ago.
Yup, it's possible. Last time I tried it, an additional dot was then added to each resource route, so you'd end up with something like this:
test..sessions.store
Not very elegant and I only needed it for one resource, so I named all of them instead. Check it out with art routes, though. Might have changed.
Last updated
2 years ago.
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast