how about
Route::controller('sessions', 'SessionsController');
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".
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.
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community