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
{{ message }}
This repository has been archived by the owner on Sep 24, 2018. It is now read-only.
What you were expecting:
When a request gets canceled it should allways dispatch a FETCH_CANCEL action, to decrease the loading count.
What happened instead:
When two requests that have {cancelPrevious: true} get fired simultaneously, the FETCH_START for both gets dispatched, one of them gets canceled, but the corresponding FETCH_CANCEL never gets dispatched. This makes the loading count become locked at a greater than 0 value forever.
Steps to reproduce:
dispatch a crudGetOne and a crudGetList simultaneously (can be for diferent resources).
Environment
Admin-on-rest version: 1.4.*
The text was updated successfully, but these errors were encountered:
ptcc
linked a pull request
May 23, 2018
that will
close
this issue
What you were expecting:
When a request gets canceled it should allways dispatch a FETCH_CANCEL action, to decrease the loading count.
What happened instead:
When two requests that have {cancelPrevious: true} get fired simultaneously, the FETCH_START for both gets dispatched, one of them gets canceled, but the corresponding FETCH_CANCEL never gets dispatched. This makes the loading count become locked at a greater than 0 value forever.
Steps to reproduce:
dispatch a crudGetOne and a crudGetList simultaneously (can be for diferent resources).
Environment
The text was updated successfully, but these errors were encountered: