-
Notifications
You must be signed in to change notification settings - Fork 77
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
Route groups #9
Comments
It's not really something I would like to add. The whole benefit of having a flat list of routes is that you can see your fully qualified routes and debug any problems, search easily etc. If you displayed groups and stuff you may as well just look at your routes file. |
Would you accept a PR if I find the time to do it? We'd love to have an On Mon, Sep 26, 2016 at 11:33 AM, Gary Green notifications@github.com
Christopher Pecoraro http://plus.google.com/u/0/+ChristopherPecoraro/ |
I would honestly prefer to have the routes grouped by url, of some kind, rather than Is there a particular reason why you want to see the routes grouped? Even with over 500 routes I haven't found the need to see the routes grouped. It's quite nice seeing all the routes and being able to easily search within the browser, scan through for any issues with missing middlewares, or parameter problems. |
Simply because we use groups and RBAC, so I would like to simply be able to view a particular "portion" of the routes. So yeah, there could be multiple ways of sorting, filtering, and searching: by namespace, group, etc... |
This will be implemented in my fork of this package: TheDragonCode#5 |
I understand that the question in this thread is very old and, apparently, Gary is busy with the main work, so I released my version from the fork as self-contained package. |
I'd like to have route groups. Have you thought about that yet?
Is anybody else working on that? Maybe I can read through the code and try to make it happen.
The text was updated successfully, but these errors were encountered: