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
There are some weird behaviors when resetting from the errorComponent if the loader returns both async and deferred data. However, if the loader returns only async data or deferred data, everything is OK.
Click the reset button again, it recovers from the errorComponent, but the route seems to reload again when it is loaded.
Remove the asyncData related code and re-run the example app.
Click the reset button, it recovers from the errorComponent and everything works fine.
Expected behavior
The first time you click the reset button, it will reset the errorComponent.
Screenshots or Videos
No response
Platform
OS: [macOS]
Browser: [Chrome]
Version: [128.0]
Additional context
No response
The text was updated successfully, but these errors were encountered:
Zebeqo
changed the title
Cannot properly reset from errorComponent if the loader returns both async and deferred data.
Cannot properly reset from errorComponent if the loader returns both async and deferred data
Sep 9, 2024
Which project does this relate to?
Router
Describe the bug
There are some weird behaviors when resetting from the
errorComponent
if the loader returns both async and deferred data. However, if the loader returns only async data or deferred data, everything is OK.Your Example Website or App
https://stackblitz.com/edit/github-oc1rey?file=src%2Froutes%2Findex.tsx
Steps to Reproduce the Bug or Issue
reset
button, nothing happens.reset
button again, it recovers from theerrorComponent
, but the route seems to reload again when it is loaded.asyncData
related code and re-run the example app.reset
button, it recovers from theerrorComponent
and everything works fine.Expected behavior
The first time you click the
reset
button, it will reset theerrorComponent
.Screenshots or Videos
No response
Platform
Additional context
No response
The text was updated successfully, but these errors were encountered: