Skip to content

bugfix: handle concurrent calls #636

Matthieu Fesselier requested to merge bugfix/636-concurrent-calls into master

I thought there were no easy fix, but actually I think I found one. @balessan @clement what do you think? Can it break something?

The idea is, when you ask for a resource, if it's in the cache already, but still in the loading list, it means that the store is still caching the dependencies of the resource. Then you have to wait until the id is removed from the loading list before resolving.

Merge request reports