Replies: 1 comment
-
Still no fix? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello!
Continuing from the issue.
In version 6.14.2 abort controllers are being cleaned up and ignored after navigation is completed, e.g. when a promise in deferred data is provided and page component which utilizes Suspense/Await for that data is rendered.
What I would love to have is the ability to automatically abort the request after the component is rendered - beforel all promises in deferred data are settled when navigating to another page. Right now the only way to do so is not using request's signal at all, but rather manually creating my own abort controller and working with it.
Desired behavior
Consider the situation below where user navigates to the /info page with some information and, say, a huge chart. User reads the description on the page and does not want to wait for the chart data to load - clicks "Home" and request to chart data is aborted, thus reducing the load on his client side and server side as well.
Beta Was this translation helpful? Give feedback.
All reactions