Misleading docs and behavior of Store.clear() about store HOT 6 OPEN

Yeah that's pretty crappy. I never found a good way to fix it. One solution is to delegate responsibility to a user's persister by calling clear. Alternatively a store can be stateful which is hard without storage. Open to suggestions 🤔

from store.

First thing that comes to mind

And on clear() we check if the resolver is the proper instance and if so, we delete the directory :)

P.S I know that this is pretty lame, and there are a lot of things to consider.
When I can find the time i will give it a proper thought and hopefully will come to a nice solution.
Cheers !

from store.

That looks reasonable. I'll think about it as well.

from store.

Any news regarding this? My use case is quite simple: Need to clean entries from disk when a user logs out. It certainly would be nice to be able to purge all entries without having to resort on "hacks", like setting a different type per user to force re-fetching when types don't match...

from store.

We are working on new version. It will have a better handle for this. Not sure release date

from store.

@mradzinski @digitalbuddha I've implemented POC that works based on my proposal above. Tried it in prod in my last app, living on the edge and stuff, and didn't find time to polish it to good PR. Shame.

from store.