getResources can sometimes error after deleting a resource
Closed this issue · 1 comments
jamesplease commented
To reproduce:
- delete a resource
- call getResources with a filter function
- observe da error
This is fixed in v3 in a breaking way (deleting the resource actually removes it from the store rather than setting it to null
), but I will be unable to make that change in v2. I am thinking I will just update the logic of getResources
to no longer explode when this occurs
jamesplease commented
Resolved in 3.0.1 and 2.4.2