fix(router): prevent 404 for routes consisting solely of an optional parameter #2798
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
ghalle
changed the title
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.
This PR fixes an issue where if a route would start with an optional parameter and would not be followed by any other segments it wouldn't be able to match without the parameter being present.
Prior to this PR creating a route like
/[[name]].tsxwould result in a url pattern like{/:name}?which would work for/foobut would fail for/After this PR, the pattern will now be
/{:name}?which matches correctly for both/and/fooRoutes containing more segments like
/[[name]]/bar.tsxwere unaffected and will retain the same pattern as before.