From ab7e1d044faed02c855270695675e1702b597e57 Mon Sep 17 00:00:00 2001 From: Jerel Miller Date: Wed, 31 Jul 2024 15:11:42 -0600 Subject: [PATCH] Fix another incorrect term --- docs/source/pagination/core-api.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/pagination/core-api.mdx b/docs/source/pagination/core-api.mdx index e13c382288f..8b64c943f0a 100644 --- a/docs/source/pagination/core-api.mdx +++ b/docs/source/pagination/core-api.mdx @@ -348,7 +348,7 @@ We recommend upgrading to version 3.11.3 or later to address bugs that exhibit u -The examples shown above use type policies to update the result of a paginated field. But what about queries that use a `no-cache` fetch policy? Data is not written to the cache, so type policies have no effect. +The examples shown above use field policies and `merge` functions to update the result of a paginated field. But what about queries that use a `no-cache` fetch policy? Data is not written to the cache, so field policies have no effect. Instead we can take advantage of the `updateQuery` option available to the `fetchMore` function. `updateQuery` gives you control over how the query is merged with the result fetched from the `fetchMore` call.