Describe the bug
Currently the state of the store is updated after refresh of the store finishes. This is fine till there are multiple store, the first store triggers a refresh, and succeeds in refreshing, but one of the other stores then fails.
The refresh state of the store now matches the refreshed configurations, but the store contents will not have been updated and will not trigger a new refresh.
To Reproduce
Steps to reproduce the behavior:
- Create a provider with two stores.
- trigger a refresh in store one, but then have store to fail to refresh.
- The provider should now not refresh as it sees the current state as the updated one not the failed one.
Describe the bug
Currently the state of the store is updated after refresh of the store finishes. This is fine till there are multiple store, the first store triggers a refresh, and succeeds in refreshing, but one of the other stores then fails.
The refresh state of the store now matches the refreshed configurations, but the store contents will not have been updated and will not trigger a new refresh.
To Reproduce
Steps to reproduce the behavior: