Allow use of UTF-8 in path parameter expressions #220
Merged
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
Add support for the `:alnum:`, `:alpha:`, `:ascii:`, `:digit:`, and `:xdigit:` POSIX character classes in URL path parameters. These values are substituted for their Java equivalent when the Route PatternBinding is created by DefaultRouter. Using the Java equivalent syntax *directly* creates complications with the existing route parameter matching expression due to nesting of curly braces. This alternative is less invasive.
decebals
added a commit
that referenced
this pull request
Oct 21, 2015
Allow use of UTF-8 in path parameter expressions
|
👍 Nice. It's for the first time when I read about |
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.
Add support for the
:alnum:,:alpha:,:ascii:,:digit:, and:xdigit:POSIX character classes in URL path parameters. These values are substituted for their Java equivalent when the Route PatternBinding is created by DefaultRouter.Using the Java equivalent syntax directly creates complications with the existing route parameter matching expression due to nesting of curly braces. This alternative is less invasive.