+8 -8

docs/api/graphcache.md

reviewed

··· 88 88 ``` 89 89 90 90 [Read more about how to set up `resolvers` on the "Computed Queries" 91 91 - page.](../graphcache/computed-queries.md) 91 91 + page.](../graphcache/local-resolvers.md) 92 92 93 93 ### `updates` option 94 94 ··· 127 127 encountered a `GraphQLError`. 128 128 129 129 [Read more about how to set up `updates` on the "Custom Updates" 130 130 - page.](../graphcache/custom-updates.md) 130 130 + page.](../graphcache/cache-updates.md) 131 131 132 132 ### `optimistic` option 133 133 ··· 152 152 | `info` | `Info` | Additional metadata and information about the current operation and the current field. [See `Info`.](#info) | 153 153 154 154 [Read more about how to set up `optimistic` on the "Custom Updates" 155 155 - page.](../graphcache/custom-updates.md) 155 155 + page.](../graphcache/cache-updates.md) 156 156 157 157 ### `schema` option 158 158 ··· 398 398 to include these fields. 399 399 400 400 [Read more about using `writeFragment` on the ["Custom Updates" 401 401 - page.](../graphcache/custom-updates.md#cachewritefragment) 401 401 + page.](../graphcache/cache-updates.md#cachewritefragment) 402 402 403 403 ### updateQuery 404 404 ··· 432 432 because all data from the cache is already a deep copy and hence we can do to it whatever we want. 433 433 434 434 [Read more about using `updateQuery` on the "Custom Updates" 435 435 - page.](../graphcache/custom-updates.md#cacheupdatequery) 435 435 + page.](../graphcache/cache-updates.md#cacheupdatequery) 436 436 437 437 ### invalidate 438 438 ··· 494 494 All utilities from extras may be imported from `@urql/exchange-graphcache/extras`. 495 495 496 496 Currently the `extras` subpackage only contains the [pagination resolvers that have been mentioned 497 497 - on the "Computed Queries" page.](../graphcache/computed-queries.md#pagination) 497 497 + on the "Computed Queries" page.](../graphcache/local-resolvers.md#pagination) 498 498 499 499 ### simplePagination 500 500 ··· 512 512 of all pages. 513 513 514 514 [Read more about `simplePagination` on the "Computed Queries" 515 515 - page.](../graphcache/computed-queries.md#simple-pagination) 515 515 + page.](../graphcache/local-resolvers.md#simple-pagination) 516 516 517 517 ### relayPagination 518 518 ··· 528 528 of all pages. 529 529 530 530 [Read more about `relayPagnation` on the "Computed Queries" 531 531 - page.](../graphcache/computed-queries.md#relay-pagination) 531 531 + page.](../graphcache/local-resolvers.md#relay-pagination) 532 532 533 533 ## The `/default-storage` import 534 534

+2 -2

docs/graphcache/README.md

reviewed

··· 31 31 - 💾 [**Custom cache resolvers**](./local-resolvers.md) Since all queries are fully resolved in the 32 32 cache before and after they're sent, you can add custom resolvers that enable you to format data, 33 33 implement pagination, or implement cache redirects. 34 34 - - 💭 [**Subscription and Mutation updates**](./custom-updates.md) You can implement update functions 34 34 + - 💭 [**Subscription and Mutation updates**](./cache-updates.md) You can implement update functions 35 35 that tell _Graphcache_ how to update its data after a mutation has been executed, or whenever a 36 36 subscription sends a new event. This allows the cache to reactively update itself without queries 37 37 having to perform a refetch. 38 38 - - 🏃 [**Optimistic mutation updates**](./custom-updates.md) When implemented, optimistic updates can 38 38 + - 🏃 [**Optimistic mutation updates**](./cache-updates.md) When implemented, optimistic updates can 39 39 provide the data that the GraphQL API is expected to send back before the request succeeds, which 40 40 allows the app to instantly render an update while the GraphQL mutation is executed in the 41 41 background.

+2 -2

docs/graphcache/offline.md

reviewed

··· 8 8 _Graphcache_ allows you to build an offline-first app with built-in offline and persistence support, 9 9 by means of adding a `storage` interface. In combination with its [Schema 10 10 Awareness](./schema-awareness.md) support and [Optimistic 11 11 - Updates](./custom-updates.md#optimistic-updates) this can be used to build an application that 11 11 + Updates](./cache-updates.md#optimistic-updates) this can be used to build an application that 12 12 serves cached data entirely from memory when a user's device is offline and still display 13 13 optimistically executed mutations. 14 14 ··· 25 25 26 26 Furthermore, if we have any mutations that the user doesn't interact with after triggering them (for 27 27 instance, "liking a post"), we can set up [Optimistic 28 28 - Updates](./custom-updates.md#optimistic-updates) for these mutations, which allows them to be 28 28 + Updates](./cache-updates.md#optimistic-updates) for these mutations, which allows them to be 29 29 reflected in our UI before sending a request to the API. 30 30 31 31 To actually now set up offline support, we'll swap out the `cacheExchange` with the

+1 -1

docs/graphcache/schema-awareness.md

reviewed

··· 136 136 have been replaced with `null`, while loading more data in the background, instead of our apps 137 137 having to wait for all data to be available. 138 138 139 139 - Let's approach this with the example from ["Computed Queries"](./computed-queries.md#resolve): We 139 139 + Let's approach this with the example from ["Computed Queries"](./local-resolvers.md#resolve): We 140 140 have our `TodosQuery` result which loads a list, and our app may want to get a specific `Todo` when 141 141 the app transitions to a details page. We may have already written a resolver that tells 142 142 _Graphcache_ what `Query.todo` does, but it may be missing some optional field to actuall give us

+1 -1

docs/graphcache/under-the-hood.md

reviewed

··· 26 26 27 27 ## Optimistic results & refetches 28 28 29 29 - We've previously learned about [how to create "Optimistic Updates" in an earlier section.](./custom-updates.md#optimistic-updates) 29 29 + We've previously learned about [how to create "Optimistic Updates" in an earlier section.](./cache-updates.md#optimistic-updates) 30 30 Optimistic updates can temporarily update cached data after incoming mutations, which will trigger on screen queries to update. 31 31 However, if we also use [the `cache-and-network` request policy](../concepts/document-caching.md#request-policies) at the same time, some queries can refetch and overwrite our optimistic data, 32 32 causing an unintended state where the intended optimistic update is destroyed.