pretty-routes
pretty-routes copied to clipboard
garygreen
Route groups
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.
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 accordion-type view "grouping" the groups, as we have 100's of routes and around ten groups with a various RBAC struture in place.
On Mon, Sep 26, 2016 at 11:33 AM, Gary Green [email protected] wrote:
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.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/garygreen/pretty-routes/issues/9#issuecomment-249523266, or mute the thread https://github.com/notifications/unsubscribe-auth/AASxzKMxS1lUyJ5oX5ClG6prTSLOQXiNks5qt5F0gaJpZM4KGT3N .
Christopher Pecoraro
http://plus.google.com/u/0/+ChristopherPecoraro/ http://twitter.com/chris__pecoraro http://facebook.com/chrispecoraro http://linkedin.com/in/chrispecoraro USA: +1 (724) 604-0210 Italy: +39 347 324 6720
I would honestly prefer to have the routes grouped by url, of some kind, rather than ::group()s. That would mean it would work for resourceful routes as well. Though I'm not sure the best way to do that, or if it would really add much value.
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: https://github.com/andrey-helldar/pretty-routes/issues/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. It's easier to look at a package than to talk about its changes: https://github.com/andrey-helldar/pretty-routes