Option to remove all cookies set with ImmortalDB about immortaldb HOT 5 CLOSED

Great. Thank you for your Issue.

Don't hesitate to let me know if there's anything else I can do for you.

from immortaldb.

Before any implementation, to make sure we're on the same page: why would you
like to clear all cookies set by ImmortalDB?

Clearing all cookies will, of course, reduce ImmortalDB's redundancy. And the
next time a key with a removed cookie is read with get(), that cookie will be
rewritten anyhow.

from immortaldb.

Hi, thanks for your reply. Yeah, my case might be an edge case, idk, you'll be judge of that:

I'm using ImmortalDB to create a rather elaborate autosaving feature for a game (played in the browser). Rather then periodically saving the whole game (which can be a lot of information), I only save the state of individual game objects (think: buildings, characters) when a meaningful change has occured. The removeAll() would be to reset game.

So to abstract the problem: Whenever cookies are set programmatically, where you might not have full control over the amount and (exact) key? I don't know if that ever happens, I thought it would be handy, but I have since solved the problem in another way.

from immortaldb.

Gotcha. Thank you for the explanation. That's helpful.

So to abstract the problem: Whenever cookies are set programmatically, where
you might not have full control over the amount and (exact) key? I don't know
if that ever happens, I thought it would be handy, but I have since solved the
problem in another way.

Deleting all keys, like keys generated dynamically, is tricky. The underlying
storage APIs -- cookies, LocalStorage, SessionStorage, etc -- don't have an easy
way to query for all keys that match a pattern.

I considered ImmortalDB keeping track of all keys that ImmortalDB has written,
but that remains out of band for now.

Did you resolve this issue independently? If so, I'll close this Issue.

from immortaldb.

I considered ImmortalDB keeping track of all keys that ImmortalDB has written,
but that remains out of band for now.

I see, well, it isn't a pressing issue I suppose and yes, I have since solved the problem by tracking the setting of the cookies in the application itself (which is arguably a more sensible way to go anyway). Thanks for your insights, appreciate it (and the project as a whole). Have a splendid day. Cheers!

from immortaldb.