Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Should ** in router match no path components #643

Open
adam-fowler opened this issue Dec 28, 2024 · 0 comments
Open

Should ** in router match no path components #643

adam-fowler opened this issue Dec 28, 2024 · 0 comments
Assignees
@Joannis

Comments

@adam-fowler
Copy link
Member

adam-fowler commented Dec 28, 2024 •
edited
Loading

Currently the router will treat ** as matching one or more path components. It seems it is more standard that ** matches zero or more path components. Making this change could be considered breaking as it is a change of behaviour.
@adam-fowler adam-fowler changed the title Should ** in router to match no path components Should ** in router match no path components Dec 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Joannis Joannis

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Joannis @adam-fowler