Skip to content

Commit 0888622

Browse files
committed
Tweak changeset
1 parent 738659b commit 0888622

2 files changed

Lines changed: 3 additions & 3 deletions

File tree

.changeset/shaggy-islands-yell.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,4 @@
22
"@apollo/client": patch
33
---
44

5-
Warn when using a `no-cache` fetch policy when a `@client` field resolves the value from the cache that defines a `read` function.
5+
Warn when using a `no-cache` fetch policy without a local resolver defined. `no-cache` queries do not read or write to the cache which meant `no-cache` queries are silently incomplete when the `@client` field value was handled by a cache `read` function.

.changeset/unlucky-cooks-rhyme.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,6 @@
22
"@apollo/client": minor
33
---
44

5-
Add an abstract `resolvesClientField` function to `ApolloCache` that can be used by 3rd party caches to determine if it can resolve a `@client` field when a local resolver is not defined.
5+
Add an abstract `resolvesClientField` function to `ApolloCache` that can be used by caches to tell `LocalState` if it can resolve a `@client` field when a local resolver is not defined.
66

7-
`LocalState` will emit a warning and set a fallback value of `null` when `resolvesClientField` returns `false`, or isn't defined. Returning `true` from `resolvesClientField` signals that a mechanism in the cache will set the field value. In this case, `LocalState` won't set the field so that `undefined` is used as the initial value.
7+
`LocalState` will emit a warning and set a fallback value of `null` when no local resolver is defined and `resolvesClientField` returns `false`, or isn't defined. Returning `true` from `resolvesClientField` signals that a mechanism in the cache will set the field value. In this case, `LocalState` won't set the field value.

0 commit comments

Comments
 (0)