v3.10.0-rc.0

Minor Changes

• #11605 e2dd4c9 Thanks @alessbell! - Adds createMockFetch utility for integration testing that includes the link chain

• #11605 e2dd4c9 Thanks @alessbell! - Adds proxiedSchema and createMockSchema testing utilities

• #11743 78891f9 Thanks @jerelmiller! - Remove alpha designation for queryRef.toPromise() to stabilize the API.

• #11743 78891f9 Thanks @jerelmiller! - Remove alpha designation for createQueryPreloader to stabilize the API.

v3.9.10

Patch Changes

• #11738 b1a5eb8 Thanks @jerelmiller! - Fix an issue where rerendering useBackgroundQuery after the queryRef had been disposed, either via the auto dispose timeout or by unmounting useReadQuery, would cause the queryRef to be recreated potentially resulting in another network request.

• #11738 b1a5eb8 Thanks @jerelmiller! - Allow queryRefs to be disposed of synchronously when a suspense hook unmounts. This prevents some situations where using a suspense hook with the same query/variables as the disposed queryRef accidentally used the disposed queryRef rather than creating a new instance.

• #11670 cc5c03b Thanks @phryneas! - Bail out of executeSubSelectedArray calls if the array has 0 elements.

v3.9.9

Patch Changes

• #11696 466ef82 Thanks @PiR1! - Immediately dispose of the queryRef if useBackgroundQuery unmounts before the auto dispose timeout kicks in.

v3.9.8

Patch Changes

• #11706 8619bc7 Thanks @jerelmiller! - Fix issue in all suspense hooks where returning an empty array after calling fetchMore would rerender the component with an empty list.

• #11694 835d5f3 Thanks @phryneas! - Expose setErrorMessageHandler from @apollo/client/dev entrypoint.

• #11689 cb8ffe5 Thanks @jerelmiller! - Fix issue where passing a new from option to useFragment would first render with the previous value before rerendering with the correct value.

• #11713 642092c Thanks @jerelmiller! - Fix issue where setting a default watchQuery option in the ApolloClient constructor could break startTransition when used with suspense hooks.

v3.10.0-alpha.1

Patch Changes

• #11465 7623da7 Thanks @alessbell! - Add watchFragment method to the cache and expose it on ApolloClient, refactor useFragment using watchFragment.

v3.9.7

Patch Changes

• #11659 652a61e Thanks @phryneas! - Make useRenderGuard more resilient to changes in React internals.

• #11594 50b1097 Thanks @alessbell! - Adds a fix for multipart subscriptions that terminate with payload: null

v3.9.6

Patch Changes

• #11617 f1d8bc4 Thanks @phryneas! - Allow Apollo Client instance to intercept hook functionality

• #11638 bf93ada Thanks @jerelmiller! - Fix issue where calling fetchMore from a suspense-enabled hook inside startTransition caused an unnecessary rerender.

v3.9.5

Patch Changes

• #11595 8c20955 Thanks @phryneas! - Bumps the dependency rehackt to 0.0.5

• #11592 1133469 Thanks @Stephen2! - Strengthen MockedResponse.newData type

• #11579 1ba2fd9 Thanks @jerelmiller! - Fix issue where partial data is reported to useQuery when using notifyOnNetworkStatusChange after it errors while another overlapping query succeeds.

• #11579 1ba2fd9 Thanks @jerelmiller! - Fix an issue where a partial cache write for an errored query would result in automatically refetching that query.

• #11562 65ab695 Thanks @mspiess! - Mocks with an infinite delay no longer require result or error

v3.9.4

Patch Changes

• #11403 b0c4f3a Thanks @jerelmiller! - Fix issue in useLazyQuery that results in a double network call when calling the execute function with no arguments after having called it previously with another set of arguments.

• #11576 e855d00 Thanks @alessbell! - Revert PR #11202 to fix caching bug reported in #11560

v3.9.3

Patch Changes

• #11525 dce923a Thanks @vezaynk! - Allows passing in client via options to useFragment

• #11558 8cba16f Thanks @alessbell! - Fix unbound-method linter error on ObservableQuery methods exposed on useQuery's QueryResult object.