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
AbortController signal is not called after pendingMs and user leaves the route.
The following sandbox simulates a long data fetching of 10 seconds when entering profile route
for the profile route and a 5 seconds pendingMs, the signal doesn't get called after 5 seconds.
Which project does this relate to?
Router
Describe the bug
AbortController signal is not called after
pendingMs
and user leaves the route.The following sandbox simulates a long data fetching of 10 seconds when entering
profile
routefor the
profile
route and a 5 seconds pendingMs, the signal doesn't get called after 5 seconds.Your Example Website or App
https://codesandbox.io/p/devbox/wm3ffd
Steps to Reproduce the Bug or Issue
pendingMs
: 5 seconds for testing purposes)profile
loader successfully fulfilled (should had been aborted as user left /profile route)(abortController signal get's called just fine within
pendingMs
time)Expected behavior
When user leaves a route, the
abortController
property of theloader
should be called whenever there's a pending promise on it's loader.Screenshots or Videos
No response
Platform
Additional context
No response
The text was updated successfully, but these errors were encountered: