Persist cache by queryKey instead of snapshot?

[pettertasolaving]

Hello! I use PersistQueryClientProvider to persist my query cache in my Expo application. It was easy to setup and seems to work fine. However, I'm wondering why it only allows saving a snapshot of the whole cache state, and not e.g one key/value per queryKey.

I have seen solutions in other discussions using dehydrateOptions to for instance ignore persisting a given query's cache. I've also looked into creating a custom persister, but it only expects methods on client level - e.g async persistClient(client: PersistedClient). I'm guessing there's a good explanation for why we can't persist specific queries instead, like persistQuery(client: PersistedClient, queryKey: string), can anyone enlighten me?

It just feels a bit odd storing my cache (700k characters) under one single key in my local key/value database...

[TkDodo]

if you want per-key persistence, you need:

• https://tanstack.com/query/latest/docs/framework/react/plugins/createPersister

[pettertasolaving]

Ah thank you, that looks spot on! Sorry, I missed it in the docs.