ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Use a cache update function with Apollo Client InMemoryCache to merge mutation results locally and avoid unnecessary refetches. Includes verification steps and limits.
Learn how to set Apollo Client InMemoryCache field policies for offset/limit and cursor-based pagination so fetchMore merges pages correctly without duplicates.
Learn how Apollo’s persisted‑queries feature shrinks request size, hardens security, and what you need to keep in sync. A step‑by‑step guide, example config, and trade‑offs are included.
Configure Apollo Client 3's InMemoryCache to merge paginated GraphQL pages instead of replacing them, with fetch-policy trade-offs and verification steps.
Apollo Client's InMemoryCache normalizes entities by ID, which breaks offset-based pagination when limit/offset aren't part of the cache key. Learn two fixes—fetchPolicy 'network-only' or custom typePolicies with keyArgs—and when each applies.
When Apollo Client returns PersistedQueryNotFound or PersistedQueryNotSupported, the server can’t process the query ID. This guide walks through the common causes, diagnostic steps, and fixes to get your persisted queries working again.
Configure Apollo Client's InMemoryCache with keyArgs:false and a merge function to append GraphQL connection pages without refetching the first page.
Learn how GraphQL persisted queries replace large query bodies with short hashes, reducing bandwidth and boosting HTTP caching, with a concrete Apollo Server/Client setup and verification steps.
When a mutation returns correct data but the UI shows stale or missing values, the cause is usually cache identity or typePolicies. Use this diagnostic guide to isolate the issue before adding refetches.
apollographql
graphql