Skip to content

Releases: apollographql/apollo-client

@apollo/client@4.0.12-beta.0

23 Dec 13:10
0e60e63

Choose a tag to compare

Pre-release

Patch Changes

@apollo/client@4.1.0-alpha.9

18 Dec 19:13
9b426d6

Choose a tag to compare

Pre-release

Minor Changes

  • #13056 b224efc Thanks @jerelmiller! - InMemoryCache no longer filters out explicitly returned undefined items from read functions for array fields. This now makes it possible to create read functions on array fields that return partial data and trigger a fetch for the full list.

  • #13058 121a2cb Thanks @jerelmiller! - Add an extensions option to cache.write, cache.writeQuery, and client.writeQuery. This makes extensions available in cache merge functions which can be accessed with the other merge function options.

    As a result of this change, any extensions returned in GraphQL operations are now available in merge in the cache writes for these operations.

Patch Changes

  • #13053 23ca0ba Thanks @phryneas! - Use memoized observable mapping when using watchFragment, useFragment or useSuspenseFragment.

@apollo/client@4.0.11

16 Dec 17:00
0775976

Choose a tag to compare

Patch Changes

  • #13050 8020829 Thanks @phryneas! - Replace usage of findLast with more backwards-compatible methods.

  • #13049 05638de Thanks @phryneas! - Fixes an issue where queries starting with skipToken or lazy queries from useLazyQuery were included in client.refetchQueries() before they had been executed for the first time. While generally queries with a standby fetchPolicy should be included in refetch, these queries never had variables passed in, so they should be excluded until they have run once and received their actual variables.

    These queries are now properly excluded from refetch operations until after their initial execution.

    This change adds a new hidden option to client.watchQuery, [variablesUnknownSymbol], which may be set true for queries starting with a fetchPolicy of standby. It will only be applied when creating the ObservableQuery instance and cannot be changed later. This flag indicates that the query's variables are not yet known, and thus it should be excluded from refetch operations until they are.
    This option is not meant for everyday use and is intended for framework integrations only.

@apollo/client@4.0.10

10 Dec 08:08
cc7c99f

Choose a tag to compare

Patch Changes

@apollo/client@4.1.0-alpha.8

05 Dec 21:02
73cc591

Choose a tag to compare

Pre-release

Minor Changes

@apollo/client@4.1.0-alpha.7

03 Dec 01:36
db71fb4

Choose a tag to compare

Pre-release

Minor Changes

@apollo/client@4.1.0-alpha.6

01 Dec 19:38
4a6c100

Choose a tag to compare

Pre-release

Patch Changes

  • #13026 05eee67 Thanks @jerelmiller! - Reduce the number of observables created by watchFragment by reusing existing observables as much as possible. This should improve performance when watching the same item in the cache multiple times after a cache update occurs.

@apollo/client@4.1.0-alpha.5

19 Nov 01:20
b0f9f97

Choose a tag to compare

Pre-release

Patch Changes

  • #13010 7627000 Thanks @jerelmiller! - Fix an issue where errors parsed from incremental chunks in ErrorLink might throw when using the GraphQL17Alpha9Handler.

  • #13010 7627000 Thanks @jerelmiller! - Handle @stream payloads that send multiple items in the same chunk when using the Defer20220824Handler.

  • #13010 7627000 Thanks @jerelmiller! - Handle an edge case with the Defer20220824Handler where an error for a @stream item that bubbles to the @stream boundary (such as an item returning null for a non-null array item) would write items from future chunks to the wrong array index. In these cases, the @stream field is no longer processed and future updates to the field are ignored. This prevents runtime errors that TypeScript would otherwise not be able to catch.

@apollo/client-graphql-codegen@2.0.0

17 Nov 21:21
55016b8

Choose a tag to compare

Major Changes

@apollo/client@4.1.0-alpha.4

17 Nov 18:31
a617c10

Choose a tag to compare

Pre-release

Patch Changes

  • #13009 259ae9b Thanks @phryneas! - Allow FragmentType not only to be called as FragmentType<TData>, but also as FragmentType<TypedDocumentNode>.

  • #13012 44706a2 Thanks @phryneas! - Add helper type QueryRef.ForQuery<TypedDocumentNode>