Solving the 'Vanishing List' Problem with Apollo Client Type Policies
Stop your paginated lists from disappearing. Learn how to use Apollo Client's typePolicies and merge functions to handle infinite scroll and custom cache keys.
Loading…
ReadMeFeed / Community knowledge
#apollo-client
Real questions. Useful conversations. Find the people who know your stack.
apollographqlDiagnosing Apollo Client Cache Inconsistency After Mutations
A step‑by‑step diagnostic guide for Apollo Client cache inconsistencies after mutations, with checks, fixes, and escalation paths.
Implementing Offset‑Based Pagination in Apollo Client with InMemoryCache
Learn how to store each page of a list under a unique cache key and use fetchMore to append new results without reloading the whole dataset.
reactUsing Cursor-Based Pagination in GraphQL to Avoid Offset Pitfalls
Learn how cursor-based pagination works in GraphQL, why it outperforms offset‑limit queries, and see a concrete Apollo Client example you can adapt.
graphqlApollo Client fetchMore Duplicates or Resets: A Cache Merge Diagnostic Guide
fetchMore can return the correct page while the normalized cache renders duplicates or snaps back to page one. Here is how to tell which cache setting is responsible.
Managing Local State in Apollo Client: Reactive Variables vs. Cache Normalization
Stop mixing Redux with Apollo. Learn how to use InMemoryCache normalization for server data and Reactive Variables for local UI state to create a single source of truth.
Managing Shared State with Apollo Client InMemoryCache Normalization
Learn how to use Apollo Client's InMemoryCache to eliminate stale data through normalization, custom typePolicies, and direct cache manipulation.
InMemoryCache typePolicies for Array Merge Strategies
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
Apollo Client cache persistence: schema version mismatch during hydration
Apollo Client utilizes apollo3-cache-persist to mirror the in-memory cache to local storage, enabling state recovery across browser sessions. During the hydration phase, the client restores the persisted state to the InMemoryCache before the application becomes interactive. A challenge arises when the application schema is updated between sessions. If the pe