You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure Route::resource was ever intended to be used this way. It might be nice to have a little more control over the URI, though – especially when working on larger projects where it makes sense to prefix URI-segments to differentiate between areas of an app.
In regard to the current implementation in Router.php – and considering that this might not be a common issue – these approaches may also be an option:
// Using a 'uri' OptionRoute::resource('user', 'Admin\\UserController', array('uri' => 'admin/user'));
// Using a 'prefix' OptionRoute::resource('user', 'Admin\\UserController', array('prefix' => 'admin'));
EDIT: Proposal #181 could be a neat solution to this as well:
I am also faced with this issue, as of now, I have removed the forward slash to make it work on my current project, however as it is proposed on #181 which can help sort this resources into a group of resources.
The most recent changes to Resource Controllers "broke" the ability to specify URI segments using slashes. Prior to the update, this would work fine:
I'm not sure
Route::resource
was ever intended to be used this way. It might be nice to have a little more control over the URI, though – especially when working on larger projects where it makes sense to prefix URI-segments to differentiate between areas of an app.In regard to the current implementation in
Router.php
– and considering that this might not be a common issue – these approaches may also be an option:EDIT: Proposal #181 could be a neat solution to this as well:
Thoughts?
The text was updated successfully, but these errors were encountered: