You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given sandbox examples on how it works from 6.22.1 (tested latest 6.22.3).
When the user is in https://rgd377.csb.app/39%2310/ and clicks "next" (which is ./next), the linked path turns /39/next which was not the case until v6.22.0.
If this is expected behaviour or fixing some bug, let me know. Currently we have to revert the app to use v6.22.0.
Expected Behavior
When the url path name contains the encoded characters, while navigating using to="./next-page" or navigate('./next-page', the path name should not be broken.
What version of React Router are you using?
6.22.1
Steps to Reproduce
Given sandbox examples on how it works from 6.22.1 (tested latest 6.22.3).
When the user is in https://rgd377.csb.app/39%2310/ and clicks "next" (which is
./next
), the linked path turns/39/next
which was not the case untilv6.22.0
.If this is expected behaviour or fixing some bug, let me know. Currently we have to revert the app to use
v6.22.0
.Expected Behavior
When the url path name contains the encoded characters, while navigating using
to="./next-page"
ornavigate('./next-page'
, the path name should not be broken.code sandbox
Actual Behavior
code sandbox
The text was updated successfully, but these errors were encountered: