feat: disallow regexp constraint in optional wildcards#77
Merged
tigerwill90 merged 1 commit intomasterfrom Feb 10, 2026
Merged
Conversation
pawndev
approved these changes
Feb 10, 2026
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.
Optional wildcards (
*{param}) can match an empty string, so allowing a regexp on them creates an ambiguity: two routes with different regexps would both match the same empty-string path, with no clear priority on who is the one matching first.This PR rejects
*{param:regexp}at registration time.Note that
+{param:regexp}is unaffected since non-optional wildcards require at least one character.