Skip to content
This repository has been archived by the owner on Sep 24, 2018. It is now read-only.

Infinite Loading #17

Open
ptcc opened this issue May 23, 2018 · 0 comments · May be fixed by #18
Open

Infinite Loading #17

ptcc opened this issue May 23, 2018 · 0 comments · May be fixed by #18

Comments

@ptcc
Copy link

ptcc commented May 23, 2018

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.*
@ptcc ptcc linked a pull request May 23, 2018 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant