dispatching abortRequests without a requestKey should abort all requests
See original GitHub issueTaking the example from https://redux-requests.klisiczynski.com/docs/api-reference/abort-requests. If i call
dispatch(abortRequests([FETCH_BOOKS]));
i am not able to abort requests FETCH_BOOKS
having a specific requestKey
. Is this the wanted behaviour or a bug?
In my case i dispatch FETCH_BOOKS
several times in a row with a different requestKey
but want to abort all requests by dispatching abortRequests
once without having to know and to set the request keys being used.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
How to Abort a Request While Navigating Away ... - Pluralsight
Dispatching the Cancel Request We will dispatch the cancel request action from the <NavBar /> component when the user clicks on a link....
Read more >Discussion of Clean Up Async Requests in `useEffect` Hooks
No, the token should be created in your useEffect call. A new token is created for every new "effect". cancel / abort is...
Read more >abort request with AbortController signal · Issue #187 ... - GitHub
For instance an autocomplete input that makes requests as key events are happening, even with a debouncer. Now in most browsers AbortController ......
Read more >Canceling Requests - Redux Resource
Many applications transfer data using HTTP requests. One feature of HTTP requests is that they can be cancelled.
Read more >Cancelling previous async action using redux-thunk
One approach would be to mark those requests as canceled by giving them random id and checking its status before handling the result....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Always having “store” in mind when talking about redux and “state” when talking about components. Thx for pointing that out.
@iwan-uschka just global redux state, suggested
getUsedRequestsKeys
is just normal redux selector, you would use it likegetQuery
from this library