ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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.
A diagnostic guide to Apollo Client pagination failures: why fetchMore duplicates or drops pages, how to inspect the normalized cache, and when to escalate.
Apollo Client's InMemoryCache uses a cache-first fetch policy by default: when a query already has cached results, reads are served from the normalized store without contacting the server. The cache has no built-in time-to-live, so entries persist indefinitely until a mutation writes new data, refetchQueries runs, or entries are evicted. The goal is to keep
Apollo Client's InMemoryCache utilizes typePolicies to define how incoming data is merged into the normalized store. When dealing with paginated lists or filtered result sets, the default merge behavior may not align with specific UI requirements for data retention or deduplication. The goal is to implement a custom merge function that prevents the overwriti
apollographql
graphql