Have Reverse Router skip 404s #176
Merged
Conversation
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
|
I think it would be preferable to skip any routes that don't have either a ControllerName or a MethodName (e.g. they are empty). Right now that is just 404s, but it's not hard to imagine adding other special actions like that |
…outing instead of just skipping routes with 404 actions. Will prevent any future special actions which do not conform to ControllerName.MethodName from causing revel to panic.
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds if statement that will skip over 404 actions when reverse routing. Since 404 action does not have a controller or method, the reverse router would panic. It doesn't make sense to try to reverse route a 404 route either. Fixes #175