[dependabot]

Bumps @apollo/client from 3.13.8 to 4.3.5.

Release notes

Sourced from @​apollo/client's releases.

@​apollo/client@​4.3.5

Patch Changes

• #13498 04b12e5 Thanks @​jerelmiller! - Fix an issue where custom scalar values that are not JSON-serializable caused errors. These values are properly serialized when used as input for variables or when used as a key field value so that cache writes and calls to cache.identify succeed.

• #13500 a23ea85 Thanks @​jerelmiller! - Require the variables option in useFragment when the fragment has required variables. This matches the behavior of useSuspenseFragment and the query hooks.

• #13501 303d80f Thanks @​kgssystem! - Parse custom scalar fields in subscription results when using the no-cache fetch policy.

@​apollo/client@​4.3.4

Patch Changes

• #13497 41d604c Thanks @​jerelmiller! - Fix an issue where a list field selected more than once with different selection sets lost the fields that only one of the selections included while a @defer boundary elsewhere in the query was still pending when using the GraphQL17Alpha9Handler. The results of all selections of the list field are now merged.

• #13457 22746bb Thanks @​phryneas! - Fixed a bug where streamFieldInfo might not have been passed into custom merge functions for @stream directives that had an aliased field in the path.

• #13457 22746bb Thanks @​phryneas! - Fix Missing field errors being logged when writing @defer results where a parent field is selected both inside and outside of a deferred fragment. Fields whose @defer boundary has not been delivered from the network are no longer reported as missing.

• #13453 9bb3a41 Thanks @​wassim-k! - Unregister the watch when an immediate cache.watch broadcast throws. Previously the watch was added to the cache before its first read, and a read that threw left the watch registered while the caller never received the unsubscribe function, so it could not be removed and every later broadcast ran into the same failing read.

• #13457 22746bb Thanks @​phryneas! - Defer20220824Handler: fix a situation where dataState would show up as completed with incremental errors instead of staying streaming.

@​apollo/client@​4.3.3

Patch Changes

• #13479 0ab2579 Thanks @​phryneas! - Fix a memory leak in isDeferredFragment/isStreamField

@​apollo/client@​4.3.2

Patch Changes

• #13467 7786771 Thanks @​SSpirate11! - Fix an unhandled AbortError promise rejection that occurred when unsubscribing from a multipart HTTP subscription.

@​apollo/client@​4.3.1

Patch Changes

• #13464 37f700e Thanks @​jerelmiller! - Fix an issue where useLazyQuery did not rerender with new variables until the network request had completed when calling execute with new variables while a request was already in-flight.

@​apollo/client@​4.3.0

Minor Changes

• #13447 24133fe Thanks @​jerelmiller! - Field policies and inputObjects can now tell the cache whether a field is a list of scalars or a scalar whose value is an array. Previously all arrays were iterated and only the inner type was provided to the scalar parse/serialize functions.

  This required some breaking changes from previous prerelease versions:

  • The field policy scalar option and inputObjects type string now use GraphQL list syntax to mark a field as a list of scalars
  • The abstract cache.getScalarForField is now cache.getScalarTypeForField and is expected to return the string representing the scalar type rather than the Scalar instance

  new InMemoryCache({

... (truncated)

Changelog

Sourced from @​apollo/client's changelog.

4.3.5

Patch Changes

• #13498 04b12e5 Thanks @​jerelmiller! - Fix an issue where custom scalar values that are not JSON-serializable caused errors. These values are properly serialized when used as input for variables or when used as a key field value so that cache writes and calls to cache.identify succeed.

• #13500 a23ea85 Thanks @​jerelmiller! - Require the variables option in useFragment when the fragment has required variables. This matches the behavior of useSuspenseFragment and the query hooks.

• #13501 303d80f Thanks @​kgssystem! - Parse custom scalar fields in subscription results when using the no-cache fetch policy.

4.3.4

Patch Changes

• #13497 41d604c Thanks @​jerelmiller! - Fix an issue where a list field selected more than once with different selection sets lost the fields that only one of the selections included while a @defer boundary elsewhere in the query was still pending when using the GraphQL17Alpha9Handler. The results of all selections of the list field are now merged.

• #13457 22746bb Thanks @​phryneas! - Fixed a bug where streamFieldInfo might not have been passed into custom merge functions for @stream directives that had an aliased field in the path.

• #13457 22746bb Thanks @​phryneas! - Fix Missing field errors being logged when writing @defer results where a parent field is selected both inside and outside of a deferred fragment. Fields whose @defer boundary has not been delivered from the network are no longer reported as missing.

• #13453 9bb3a41 Thanks @​wassim-k! - Unregister the watch when an immediate cache.watch broadcast throws. Previously the watch was added to the cache before its first read, and a read that threw left the watch registered while the caller never received the unsubscribe function, so it could not be removed and every later broadcast ran into the same failing read.

• #13457 22746bb Thanks @​phryneas! - Defer20220824Handler: fix a situation where dataState would show up as completed with incremental errors instead of staying streaming.

4.3.3

Patch Changes

• #13479 0ab2579 Thanks @​phryneas! - Fix a memory leak in isDeferredFragment/isStreamField

4.3.2

Patch Changes

• #13467 7786771 Thanks @​SSpirate11! - Fix an unhandled AbortError promise rejection that occurred when unsubscribing from a multipart HTTP subscription.

4.3.1

Patch Changes

• #13464 37f700e Thanks @​jerelmiller! - Fix an issue where useLazyQuery did not rerender with new variables until the network request had completed when calling execute with new variables while a request was already in-flight.

4.3.0

Minor Changes

• #13447 24133fe Thanks @​jerelmiller! - Field policies and inputObjects can now tell the cache whether a field is a list of scalars or a scalar whose value is an array. Previously all arrays were iterated and only the inner type was provided to the scalar parse/serialize functions.

  This required some breaking changes from previous prerelease versions:

... (truncated)

Commits

• f3d28a5 Version Packages (#13503)
• c71e76c Avoid mutating the raw network result object when handling subscription resul...
• 303d80f Parse custom scalars in subscriptions with no-cache fetch policy (#13501)
• 04b12e5 Handle non-JSON-serializable scalar value in cache.identify and `cache.watc...
• a23ea85 Make sure variables option is required for useFragment if it has required...
• 91591db Version Packages (#13488)
• 41d604c Fix an edge case where a pending @defer might lose data for fields in a lis...
• 22746bb Prevent "missing field" error logging for overlapping nested deferred fields....
• 335f1ea Improve documentation of cache redirects (#13496)
• 946e3af chore(deps): update dependency vitest to v4 [security] (#13491)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​apollo/client since your current version.

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 87b43dfc-abf7-40e4-a2ca-5dae08ef3a27

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot recreate.

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.