Skip to content
Discussion options

You must be logged in to vote

offlineExchange is for persistence/offline-first behavior; it is not a global “never hit the network” switch. If you want a tier that runs only from local data, use requestPolicy: 'cache-only' for those operations, or build that client without fetchExchange at all.

The null result usually means Graphcache cannot fully satisfy that exact query from the normalized cache. Being “online once” is not enough unless the previous operations wrote all requested entities/fields and Graphcache can resolve the query shape. For a local-only tier, make the cache schema-aware, add keys/resolvers for non-id objects, and add mutation updates/optimistic writes so every offline query can be answered from th…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by mikeaustin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants