Martin Janeček

> Currently this implementation saves the entire cache as a single value Actually, that depends on the `serialize` option. With `serialize: false` and compatible driver (only LocalForage as of now...

The *eventually* could be the key here. To forcefully clear the storage, call `persistor.purge()` as illustrated in the example: https://github.com/apollographql/apollo-cache-persist/blob/405de6fb1e963ab50fa30633fb5e000f91d40540/examples/web/src/App.tsx#L100-L105 `client.clearStorage()` clears the apollo client storage (sets it to an...

> is there actually a use-case for not purging when the store is cleared I'm not aware of such use-case. The only reason I could think of is that purging...

Is this for [MMKVStorageWrapper](https://github.com/apollographql/apollo-cache-persist/blob/master/src/storageWrappers/MMKVStorageWrapper.ts) or [MMKVWrapper](https://github.com/apollographql/apollo-cache-persist/blob/master/src/storageWrappers/MMKVWrapper.ts)? In both cases, wrappers use `set`/`setItem`, which should override any existing value instead of adding a new duplicate key. If you're experiencing a different...

I wasn't aware of that. But since it's *just implementation detail*, it doesn't affect the functionality of cache persistor. Feel free to send a PR updating the docs, preferably adding...

I understand your concern, but there's nothing we can do about it on our side (other than warning about this this in the docs). Like mentioned in the linked issues,...

Not really, we only clear the storage on logout, no other mechanism was needed. I'm guessing the mmkv integrations or mmkv itself has some kind of GC built in, else...

I believe nothing has really changed at apollo-cache-persist's options regarding cache expiration since it was last discussed in #2 and #53. Here a few mentions worth exploring: > If your...

@jinowac what's the problem? Could you provide more details on the expected behaviour vs. the actual behaviour? Minimal reproducible example would be helpful. In general, you'll probably need separate persistors...

Hello! I believe we don't have any specific support for local-only fields. Does the result of your field's policy `read()` function get persisted? There was a [custom Persistence Mapper example](https://github.com/apollographql/apollo-cache-persist/tree/a0b45608ffe501c50fc34e2968fd53962fb27ce6/examples/react-native/src/utils/persistence)...