-
-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
Wildcards in route names #61
Comments
Never mind
Seems to do the trick. |
Sorry for necroing an old thread. I've never see this in the documentation. Can anyone verify? |
@srph I'm gonna necro to answer your question. One way to match is to just not have a react-router docs says:
If you look at the package.json of react-router on npm, you will see the dependency The most recent path-to-regxp broke compatibility with the older versions, so that's why react-router stays on
|
Is there a notion of a "catch-all" or default route?
Or routes that match based on globs or regular expressions?
The text was updated successfully, but these errors were encountered: