This repository has been archived by the owner on Jun 11, 2022. It is now read-only.
Use Devise.router_name when mounted inside an engine #6
Conversation
This file contains 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
|
This is very similar to heartcombo/devise#2854 |
maeve
pushed a commit
that referenced
this pull request
Feb 5, 2014
Use Devise.router_name when mounted inside an engine
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When mounted inside another engine, the route helpers called by this gem may be namespaced. Devise handles this by setting up a
Devise.router_nameconfiguration option in the devise initializer, Our url helpers should respect this config instead of assuming that the routes will be mounted in the main application.