-
-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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.
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
add support for an array of paths in <Route> and matchPath #5889
Conversation
5654844
to
6bc2f8a
Compare
fb3a586
to
f9481bb
Compare
This comment has been minimized.
This comment has been minimized.
8f33936
to
1fb8696
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Would also love to see this merged, definitely willing to help out if it needs any more work. |
This comment has been minimized.
This comment has been minimized.
Why wait for #5866 when this PR is already working? |
7cd7864
to
92582d3
Compare
92582d3
to
4b79b96
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great, thanks @baronswindle! And thank you for rebasing on top of all the changes from the past few weeks 😅
Just FYI everyone, this was just released in version 4.4.0-beta.4. You can try it out now by installing from the
|
Hey! That looks nice, but what about support of RegExp in paths?! react-route is still not fully same as it is in https://github.com/pillarjs/path-to-regexp, which supports RegExp |
I piggybacked off of the tests written for
matchPath()
by @Shervanator at #5393, and I'm tackling the issue described by @mjackson at #5866.<Route>
andmatchPath()
match.path
is a stringI'm happy to add docs and examples if everybody is satisfied with the behavior. Let me know if you think any changes are in order as well.