-
-
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]: Rendering solo NavLink with <MemoryRouter> causes error #11057
Comments
This looks like it's an issue when rendering a |
This workaround failed for me and I came up with this instead (you can replace BrowserRouter with MemoryRouter):
|
Oops - yeah sorry I thought that was assumed - a |
Same issue? link |
@phoskee Not quite - you need to be including a Router component somewhere in order to use |
This is resolved by #11062 and will be available in the next release |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
What version of React Router are you using?
6.20.0
Steps to Reproduce
Starting from 6.19.0 I get an error with using the combination relative="path" and an absolute path in the to-field of a NavLink. A real life usage is then the to-attribute is an input parameter for a wrapper-class.
Expected Behavior
The testcase should not fail
Actual Behavior
The text was updated successfully, but these errors were encountered: