-
-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
[Bug]: Can't start route with @ within Layout Routes #8699
Comments
Relates to #8525 (comment). Probably needs a closer look at the spec w.r.t |
@brophdawg11 - please note that the @ character already works in 6.2.2, just not within layout routes.
My PR fixes this issue |
I was running into the same issue and agree with @theostavrides:
|
In #8563 I was specifically only including the unreserved characters with the idea that the whitelist could be expanded if needed. Of the reserved characters in the RFC, only
|
Not merged PR yet. https://gist.github.com/kgamecarter/b64731e71aeecaa373aa31f81f8a1a43 |
the #8877 will release in 6.4.0? |
Hey folks! We've been doing some work lately to ensure that we can fully support special characters in paths and params etc. If anyone has a moment and would like to give Here's a stackblitz with some example routes, so feel free to fork it and add any special scenarios you have in your apps and let us know if anything seems off! |
In new versions of react-router-dom 6.5.x and 6.6.x special characters like Here is updated stackblitz from @brophdawg11 with example of broken routes using |
Is there a way to downgrade while using remix? I've given up on trying to get this working with the filesystem-based routing, and now attempting to define a route in remix.config.js as |
You can still use special characters, but dynamic parameters ( I'm going to close this issue out since I think this specific issue has been fixed since 6.4.3 but we missed closing it upon release. |
What version of React Router are you using?
react-router-dom 6.2.2
Steps to Reproduce
/@tom
in the browserExpected Behavior
/@tom
should matchpath=":id"
, and render the element to the screenActual Behavior
The path does not match and this message is printed in the console:
index.tsx:25 No routes matched location "/@tom"
Notes
This issue is related to #8563, which was put into release 6.2.2.
The text was updated successfully, but these errors were encountered: