-
-
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
[Bug]: Nested routes not matching #8127
Comments
Note, this still persists with beta 7. |
So I'll copy paste here what I had In above "duplicate" bug report. Interesting thing is that the Navigation component got rendered but visuals ones didn't, you can check it in codesandbox I've linked. The bug is in react-router-dom as bumping it to beta.6 and above creates this issue (its still present in beta.8) Test Case Steps to reproduce
Expected Behavior Actual Behavior |
@Monar It's already fixed and both issues have been closed. See the commit in your original issue. |
What version of React Router are you using?
6.0.0-beta.6
Steps to Reproduce
In my parent component I have:
And then in
<SubComponent />
I have:None of the routes in
<SubComponent />
match. This was working in beta 5, so I'm not sure if this is a bug or the behavior has changed slightly.The text was updated successfully, but these errors were encountered: