Skip to content

Releases: apollographql/apollo-client

v3.10.2

03 May 16:41
d290196
Compare
Choose a tag to compare

Patch Changes

  • #11821 2675d3c Thanks @jerelmiller! - Fix a regression where rerendering a component with useBackgroundQuery would recreate the queryRef instance when used with React's strict mode.

  • #11821 2675d3c Thanks @jerelmiller! - Revert the change introduced in
    3.9.10 via #11738 that disposed of queryRefs synchronously. This change caused too many issues with strict mode.

v3.10.1

24 Apr 18:42
7f53db9
Compare
Choose a tag to compare

Patch Changes

v3.10.0

24 Apr 16:03
5f65439
Compare
Choose a tag to compare

Minor Changes

Patch Changes

  • #11757 9825295 Thanks @phryneas! - Adjust useReadQuery wrapper logic to work with transported objects.

  • #11771 e72cbba Thanks @phryneas! - Wrap useQueryRefHandlers in wrapHook.

  • #11754 80d2ba5 Thanks @alessbell! - Export WatchFragmentOptions and WatchFragmentResult from main entrypoint and fix bug where this wasn't bound to the watchFragment method on ApolloClient.

v3.10.0-rc.1

15 Apr 23:17
a4c89f0
Compare
Choose a tag to compare
v3.10.0-rc.1 Pre-release
Pre-release

Minor Changes

Patch Changes

  • #11757 9825295 Thanks @phryneas! - Adjust useReadQuery wrapper logic to work with transported objects.

  • #11771 e72cbba Thanks @phryneas! - Wrap useQueryRefHandlers in wrapHook.

  • #11754 80d2ba5 Thanks @alessbell! - Export WatchFragmentOptions and WatchFragmentResult from main entrypoint and fix bug where this wasn't bound to the watchFragment method on ApolloClient.

v3.9.11

10 Apr 13:55
8bc7d4d
Compare
Choose a tag to compare

Patch Changes

  • #11769 04132af Thanks @jerelmiller! - Fix an issue where using skipToken or the skip option with useSuspenseQuery in React's strict mode would perform a network request.

v3.10.0-rc.0

02 Apr 20:58
7699f43
Compare
Choose a tag to compare
v3.10.0-rc.0 Pre-release
Pre-release

Minor Changes

v3.9.10

01 Apr 18:52
e8556c3
Compare
Choose a tag to compare

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

22 Mar 19:44
6393537
Compare
Choose a tag to compare

Patch Changes

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

v3.9.8

20 Mar 19:08
a0d114e
Compare
Choose a tag to compare

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

18 Mar 19:52
Compare
Choose a tag to compare
v3.10.0-alpha.1 Pre-release
Pre-release

Patch Changes

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