Ensure route collisions don't occur with admin/controller/batch_action and admin/controller/:id (#show)#49
Merged
andreibondarev merged 1 commit intoSourceLabsLLC:mainfrom Apr 2, 2026
Conversation
…on` and `admin/controller/:id` (#show)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
When #47 was merged it opened the possibility for
admin/controller/actionstyle url routes to conflict with existingadmin/controller/:id#show endpoint. This PR uses the gem's name to prefix the route to avoid collisions.For example
Admin::MyController#some_batch_action => admin/my_controller/some_batch_action
Admin::MyController#show => admin/my_controller/:id
In this case
admin/my_controller/:idwill likely be defined before the dynamically generated batch_action routesWhat
administrate_batch_actions/to routes