Bump @apollo/client from 3.2.1 to 3.4.8 in /gsa

[dependabot]

Bumps @apollo/client from 3.2.1 to 3.4.8.

Release notes

Sourced from @​apollo/client's releases.

3.4.0

Apollo Client 3.4.0

New documentation

• Refetching queries with client.refetchQueries. @​StephenBarlow and @​benjamn in #8265

Improvements

• InMemoryCache now guarantees that any two result objects returned by the cache (from readQuery, readFragment, etc.) will be referentially equal (===) if they are deeply equal. Previously, === equality was often achievable for results for the same query, on a best-effort basis. Now, equivalent result objects will be automatically shared among the result trees of completely different queries. This guarantee is important for taking full advantage of optimistic updates that correctly guess the final data, and for "pure" UI components that can skip re-rendering when their input data are unchanged. @​benjamn in #7439

• Mutations now accept an optional callback function called onQueryUpdated, which will be passed the ObservableQuery and Cache.DiffResult objects for any queries invalidated by cache writes performed by the mutation's final update function. Using onQueryUpdated, you can override the default FetchPolicy of the query, by (for example) calling ObservableQuery methods like refetch to force a network request. This automatic detection of invalidated queries provides an alternative to manually enumerating queries using the refetchQueries mutation option. Also, if you return a Promise from onQueryUpdated, the mutation will automatically await that Promise, rendering the awaitRefetchQueries option unnecessary. @​benjamn in #7827

• Support client.refetchQueries as an imperative way to refetch queries, without having to pass options.refetchQueries to client.mutate. @​dannycochran in #7431

• Improve standalone client.refetchQueries method to support automatic detection of queries needing to be refetched. @​benjamn in #8000

• Fix remaining barriers to loading @apollo/client/core as native ECMAScript modules from a CDN like esm.run. Importing @apollo/client from a CDN will become possible once we move all React-related dependencies into @apollo/client/react in Apollo Client 4. @​benjamn in #8266

• InMemoryCache supports a new method called batch, which is similar to performTransaction but takes named options rather than positional parameters. One of these named options is an onDirty(watch, diff) callback, which can be used to determine which watched queries were invalidated by the batch operation. @​benjamn in #7819

• Allow merge: true field policy to merge Reference objects with non-normalized objects, and vice-versa. @​benjamn in #7778

• Allow identical subscriptions to be deduplicated by default, like queries. @​jkossis in #6910

• Always use POST request when falling back to sending full query with @apollo/client/link/persisted-queries. @​rieset in #7456

• The FetchMoreQueryOptions type now takes two instead of three type parameters (<TVariables, TData>), thanks to using Partial<TVariables> instead of K extends typeof TVariables and Pick<TVariables, K>. @​ArnaudBarre in #7476

• Pass variables and context to a mutation's update function. Note: The type of the update function is now named MutationUpdaterFunction rather than MutationUpdaterFn, since the older type was broken beyond repair. If you are using MutationUpdaterFn in your own code, please use MutationUpdaterFunction instead. @​jcreighton in #7902

• A resultCacheMaxSize option may be passed to the InMemoryCache constructor to limit the number of result objects that will be retained in memory (to speed up repeated reads), and calling cache.reset() now releases all such memory. @​SofianHn in #8701

• Fully remove result cache entries from LRU dependency system when the corresponding entities are removed from InMemoryCache by eviction, or by any other means. @​sofianhn and @​benjamn in #8147

• Expose missing field errors in results.

... (truncated)

Changelog

Sourced from @​apollo/client's changelog.

Apollo Client 3.4.8

Bug Fixes

• Fix error thrown by nested keyFields: ["a", ["b", "c"], "d"] type policies when writing results into the cache where any of the key fields (.a, .a.b, .a.c, or .d) have been renamed by query field alias syntax. @​benjamn in #8643

• Fix regression from PR #8422 (first released in @apollo/client@3.4.0-rc.15) that caused result.data to be set to undefined in some cases after ObservableQuery#getCurrentResult reads an incomplete result from the cache. @​benjamn in #8642

Apollo Client 3.4.7

Bug Fixes

• Fix accidental reuse of recycled MergeTree objects in StoreWriter class used by InMemoryCache. @​benjamn in #8618

Apollo Client 3.4.6

Improvements

• Reevaluate window.fetch each time HttpLink uses it, if not configured using options.fetch. This change enables a variety of strategies for instrumenting window.fetch, without requiring those strategies to run before @apollo/client/link/http is first imported. @​benjamn in #8603

• Clarify mutation fetchPolicy options ("network-only" or "no-cache") using MutationFetchPolicy union type. @​benjamn in #8602

Bug Fixes

• Restore full @apollo/client/apollo-client.cjs.js CommonJS bundle for older bundlers.

  Note that Node.js and CommonJS bundlers typically use the bundles specified by "main" fields in our generated package.json files, which are all independent and non-overlapping CommonJS modules. However, apollo-client.cjs.js is just one big bundle, so mixing imports of apollo-client.cjs.js with the other CommonJS bundles is discouraged, as it could trigger the dual package hazard. In other words, please don't start using apollo-client.cjs.js if you're not already.

  @​benjamn in #8592

• Log MissingFieldErrors in ObservableQuery#getCurrentResult using invariant.debug, rather than reporting them via result.error. @​benjamn in #8604

Apollo Client 3.4.5

Bug Fixes

• Fix double registration bug for mutation refetchQueries specified using legacy one-time refetchQueries: [{ query, variables }] style. Though the bug is fixed, we recommend using refetchQueries: [query] instead (when possible) to refetch an existing query using its DocumentNode, rather than creating, executing, and then deleting a new query, as the legacy { query, variables } style unfortunately does. @​benjamn in #8586

• Fix useQuery/useLazyQuery stalling when clients or queries change. @​brainkim in #8589

Apollo Client 3.4.4

... (truncated)

Commits

• 87ca9d8 Bump @​apollo/client npm version to 3.4.8.
• 47c5755 Merge pull request #8642 from apollographql/avoid-voiding-result.data-in-getC...
• ef3ffe2 Mention PR #8642 in CHANGELOG.md.
• 9b8a507 Shallow-clone variables before calling this.fetch.
• c834089 Capture options.variables in ObservableQuery#reobserve.
• e1a1ceb Remove inaccurate/unnecessary getLastResult comment.
• 7a6a016 Bump bundlesize limit from 24.6kB to 24.7kB (now 24.61kB).
• 9795754 Fix useQuery test to provide missing result.data.
• 8b60b29 Avoid using stale last.result in getCurrentResult.
• 8062a48 Allow getLast{Result,Error} to enforce variables equality.
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #96.