-
-
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
Fix pathless relative routing with a basename #10433
Conversation
🦋 Changeset detectedLatest commit: 55835d7 The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@@ -3094,7 +3094,7 @@ function normalizeTo( | |||
let path = resolveTo( | |||
to ? to : ".", | |||
getPathContributingMatches(contextualMatches).map((m) => m.pathnameBase), | |||
location.pathname, | |||
stripBasename(location.pathname, basename) || location.pathname, |
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.
useLocation
strips this off so this code brought in from the react layer lost that since the raw router location contains the basename
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
Basename is duplicated when calling useNavigate using 6.11.1, but 6.11.0 is work fine |
Fixed by #10492 - available in |
Closes #10431