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
When doing an async work in unstable_patchRoutesOnNavigation, the page change should match the patched route, even when a second navigation start at the same url while unstable_patchRoutesOnNavigation is still running.
Actual Behavior
When you click on the link to /test, the routing works fine after 1sec, but if you do double click, it goes to the 404 page.
unstable_patchRoutesOnNavigation is called once, but the second routing forever "associate" the /test page to the 404 page (try to navigate back and go to /test again,), until you restart the app.
The text was updated successfully, but these errors were encountered:
We just published version 6.27.0-pre.0 which involves this issue. If you'd like to take it for a test run please try it out and let us know what you think!
What version of React Router are you using?
6.26.2
Steps to Reproduce
https://stackblitz.com/edit/github-tgrtuk-oqthfq?file=src%2Fapp.tsx
Expected Behavior
When doing an async work in
unstable_patchRoutesOnNavigation
, the page change should match the patched route, even when a second navigation start at the same url whileunstable_patchRoutesOnNavigation
is still running.Actual Behavior
When you click on the link to /test, the routing works fine after 1sec, but if you do double click, it goes to the 404 page.
unstable_patchRoutesOnNavigation
is called once, but the second routing forever "associate" the /test page to the 404 page (try to navigate back and go to /test again,), until you restart the app.The text was updated successfully, but these errors were encountered: