chore(deps): bump @apollo/client from 3.0.0-beta.44 to 3.4.3 in /Services/UI

[dependabot-preview]

Bumps @apollo/client from 3.0.0-beta.44 to 3.4.3.

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.3

Bug Fixes

• Fix { ssr: false } causing queries to hang on the client. @​brainkim in #8574

Apollo Client 3.4.2

Bug Fixes

• Use more default type parameters for mutation-related types in react/types/types.ts, to provide smoother backwards compatibility for code using those types explicitly. @​benjamn in #8573

Apollo Client 3.4.1

Bug Fixes

• Initialize stringifyCanon lazily, when canonicalStringify is first called, fixing Uncaught ReferenceError: __DEV__ is not defined errors due to usage of __DEV__ before declaration. @​benjamn in #8557

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

... (truncated)

Commits

• b4b859b Bump @​apollo/client npm version to 3.4.3.
• 5956a38 Merge pull request #8574 from apollographql/brian-ssr-false
• 2d3262b Update CHANGELOG.md
• b413b93 fix ssr: false not starting queries #8571
• b472ebe add failing test for useQuery and ssr: false
• b8b831f Merge pull request #8543 from apollographql/brian-testing
• ea460cc attempt to prevent some testing-library flakiness
• 91e0383 fix some skip tests
• 77c7873 address feedback
• 4d3d14b refactor some more mutation tests
• 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 use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)