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
Routing specs and cleanup #1477
Conversation
It still works, and it cleans up the output of `rake routes`.
Also cleans up some alignment and removes unnecessary "to: " arguments
Handles stuff that's shared across admin controllers.
We were already calling `authorize_admin_issue!` in a before filter with the same permission checks, so this deleted check wasn't actually doing anything.
Uses TeamMembers#index instead, to be more RESTful
Wouldn't it be better to split the routing specs into one file per controller? |
Yeah, probably. I can do that if we want. |
I dunno, while there's definitely a downside to a file that big, I think there's definitely a positive side to seeing them all in one file; so many of them are related since they belong to Projects. There's probably a better way to split it up than just one file per controller. I'll think on it some more. |
I'll trust your jundgement. ;) |
That split them up a bit. |
Routing specs and cleanup
@tsigo great cleanup. You make my dreams :) |
API MR ordering Fixes #1477 See merge request !1076
Use `search_text_nodes` helper in our custom filters Closes #1477 See merge request !561
First, this adds routing specs. Why? Because I was going to modify the
routes and wanted to make sure the current ones still worked after my
changes.
Then I made a few changes:
AdminController
base controller for the other Admincontrollers to subclass. It currently handles setting the layout and
authorizing an admin and just removes some duplication from those
controllers.
routes.rb
, mostly 1.9 Hash syntax and alignment andspacing.
controllers.
actions but only used "show", for instance.)
uses the 'index' action in TeamMembers.