-
Notifications
You must be signed in to change notification settings - Fork 424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should --view-path="admin" Be used in Routes/Redirects/etc #28
Comments
Hi @vita10gy, --view-path="admin" option will let you separate the view files. If you like to put your controller to separate directory and want to add prefix on route as well then Make the route as like Route::group(['prefix' => 'admin', 'namespace' => 'Admin'], function () { Make your controller namespace as like Put the controller file to the directory Thanks |
How possible would making some parameter to automate that be? |
I will be added this feature soon. |
Hi @vita10gy check this features on new version. |
To say I'm "very new to Laravel" would be an understatement, but we're looking to transition from a custom thing to something like laravel. One of the things I like about our custom approach is we can generate a full CRUD process from a given DB table. Hence why I'm interested in this project.
We like to have all these admin things in /admin/ (though might not be the end of the world to let that go) and I see you have --view-path="admin" as an option. Problem is it only seems to matter for the blades (which I realize is the views).
However, if you do that, nothing seems to work until you get everything else working at /admin/widget which takes a change to the route file, any urls in the blades, and the redirects in the controller.
Am I missing something obvious, or should all those other changes be implied by --view-path="admin" as well?
The text was updated successfully, but these errors were encountered: