fix(frontend): update dependency @apollo/client to v3.7.15 - autoclosed #292
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.7.1
->3.7.15
Release Notes
apollographql/apollo-client
v3.7.15
Compare Source
Patch Changes
#10891
ab42a5c08
Thanks @laverdet! - Fixes a bug in how multipart responses are read when using@defer
. When reading a multipart body,HttpLink
no longer attempts to parse the boundary (e.g."---"
or other boundary string) within the response data itself, only when reading the beginning of each mulitpart chunked message.#10789
23a4e1578
Thanks @phryneas! - Fix a bug where other fields could be aliased to__typename
orid
, in which case an incoming result would be merged into the wrong cache entry.v3.7.14
Compare Source
Patch Changes
#10764
1b0a61fe5
Thanks @phryneas! - DeprecateuseFragment
returnPartialData
option#10810
a6252774f
Thanks @dleavitt! - Fix type signature ofServerError
.In <3.7
HttpLink
andBatchHttpLink
would return aServerError.message
of e.g."Unexpected token 'E', \"Error! Foo bar\" is not valid JSON"
and aServerError.result
ofundefined
in the case where a server returned a >= 300 response code with a response body containing a string that could not be parsed as JSON.In >=3.7,
message
became e.g.Response not successful: Received status code 302
andresult
became the string from the response body, however the type inServerError.result
was not updated to include thestring
type, which is now properly reflected.v3.7.13
Compare Source
Patch Changes
#10805
a5503666c
Thanks @phryneas! - Fix a potential memory leak in SSR scenarios when manypersistedQuery
instances were created over time.#10718
577c68bdd
Thanks @Hsifnus! - Delay Concast subscription teardown slightly inuseSubscription
to prevent unexpected Concast teardown when oneuseSubscription
hook tears down its in-flight Concast subscription immediately followed by anotheruseSubscription
hook reusing and subscribing to that same Concastv3.7.12
Compare Source
Patch Changes
895bcdcff
Thanks @alessbell! - If a multipart chunk contains onlyhasNext: false
, immediately complete the observable.v3.7.11
Compare Source
Patch Changes
#10586
4175af594
Thanks @alessbell! - Improve WebSocket error handling for genericEvent
received on error. For more information see https://developer.mozilla.org/en-US/docs/Web/API/WebSocket/error_event.#10411
152baac34
Thanks @lovasoa! - Simplify error message generation and make 'undefined' an impossible message string.#10592
cdb98ae08
Thanks @alessbell! - Adds support for multipart subscriptions inHttpLink
.#10698
38508a251
Thanks @jerelmiller! - Changes the behavior ofuseLazyQuery
introduced in #10427 where unmounting a component before a query was resolved would reject the promise with an abort error. Instead, the promise will now resolve naturally with the result from the request.Other notable fixes:
useLazyQuery
with a different query document will now ensure the execution function uses the updated query document. Previously, only the query document rendered the first time would be used for the request.#10660
364bee98f
Thanks @alessbell! - Upgrades TypeScript to v5. This change is fully backward-compatible and transparent to users.#10597
8fb9d190d
Thanks @phryneas! - Fix a bug where an incoming cache update could prevent future updates from the active link.#10629
02605bb3c
Thanks @phryneas! -useQuery
: delay unsubscribe to fix race conditionsv3.7.10
Compare Source
Patch Changes
#9438
52a9c8ea1
Thanks @dciesielkiewicz! - Ensure theclient
option passed touseMutation
's execute function is used when provided. Previously this option was ignored.#9124
975b923c0
Thanks @andrebrantom! - MakeApolloClient.writeQuery
andApolloClient.writeFragment
behave more likecache.writeQuery
andcache.writeFragment
by returning the reference returned by the cache.v3.7.9
Compare Source
Patch Changes
#10560
a561ecf43
Thanks @benjamn! - Keep__typename
fragment when it does not contain@client
directive and strip out inline fragments which use a@client
directive. Thanks @Gazler and @mtsmfm!#10560
251a12806
Thanks @benjamn! - RefactorremoveDirectivesFromDocument
to fix AST ordering sensitivities and avoid 1/3 AST traversals, potentially improving performance for large queriesv3.7.8
Compare Source
Patch Changes
#7555
45562d6fa
Thanks @TheCeloReis! - AddsTVariables
generic toGraphQLRequest
andMockedResponse
interfaces.#10526
1d13de4f1
Thanks @benjamn! - Tolerate undefinedconcast.sources
ifcomplete
called earlier thanconcast.start
#10497
8a883d8a1
Thanks @nevir! - UpdateSingleExecutionResult
andIncrementalPayload
'sdata
types such that they no longer includeundefined
, which was not a valid runtime value, to fix errors when TypeScript'sexactOptionalPropertyTypes
is enabled.v3.7.7
Compare Source
Patch Changes
#10502
315faf9ca
Thanks @jerelmiller! - Log a warning to the console when a mock passed toMockedProvider
orMockLink
cannot be matched to a query during a test. This makes it easier to debug user errors in the mock setup, such as typos, especially if the query under test is using anerrorPolicy
set toignore
, which makes it difficult to know that a match did not occur.#10499
9e54f5dfa
Thanks @phryneas! - Allow the execution function returned byuseLazyQuery
to change the query.#10362
14a56b105
Thanks @mccraveiro! - Fix error when server returns an error and we are also querying for a local fieldv3.7.6
Compare Source
Patch Changes
#10470
47435e879
Thanks @alessbell! - Bumps TypeScript to4.9.4
(previously4.7.4
) and updates types to account for changes in TypeScript 4.8 by propagating contstraints on generic types. Technically this makes some types stricter as attempting to passnull|undefined
into certain functions is now disallowed by TypeScript, but these were never expected runtime values in the first place.This should only affect you if you are wrapping functions provided by Apollo Client with your own abstractions that pass in their generics as type arguments, in which case you might get an error like
error TS2344: Type 'YourGenericType' does not satisfy the constraint 'OperationVariables'
. In that case, make sure thatYourGenericType
is restricted to a type that only accepts objects viaextends
, likeRecord<string, any>
or@apollo/client
'sOperationVariables
:#10408
55ffafc58
Thanks @zlrlo! - fix: modify BatchHttpLink to have a separate timer for each different batch key#9573
4a4f48dda
Thanks @vladar! - Improve performance of local resolvers by only executing selection sets that contain an@client
directive. Previously, local resolvers were executed even when the field did not contain@client
. While the result was properly discarded, the unncessary work could negatively affect query performance, sometimes signficantly.v3.7.5
Compare Source
Patch Changes
#10458
b5ccef229
Thanks @lennyburdette! - PassesgetServerSnapshot
touseSyncExternalStore
so that it doesn't trigger aMissing getServerSnapshot
error when usinguseFragment_experimental
on the server.#10471
895ddcb54
Thanks @alessbell! - More robust type definition forheaders
property passed tocreateHttpLink
#10321
bbaa3ef2d
Thanks @alessbell! - Refetch should not return partial data witherrorPolicy: none
andnotifyOnNetworkStatusChange: true
.#10402
0b07aa955
Thanks @Hugodby! - Improve context types#10469
328c58f90
Thanks @jerelmiller! - Add generic type defaults when usinguseFragment
to allow passingTData
directly to the function without needing to specifyTVars
.v3.7.4
Compare Source
Patch Changes
#10427
28d909cff
Thanks @jerelmiller! - Ensure in-flight promises executed byuseLazyQuery
are rejected whenuseLazyQuery
unmounts.#10383
5c5ca9b01
Thanks @jerelmiller! - Ensure theonError
callback is called when theerrorPolicy
is set to "all" and partial data is returned.#10425
86e35a6d2
Thanks @jerelmiller! - Prefer theonError
andonCompleted
callback functions passed to the execute function returned fromuseMutation
instead of calling both callback handlers.v3.7.3
Compare Source
Patch Changes
#10334
7d923939d
Thanks @jerelmiller! - Better handle deferred queries that have cached or partial cached data for them#10368
46b58e976
Thanks @alessbell! - Fix: unblocks support for defer in mutationsIf the
@defer
directive is present in the document passed tomutate
, the Promise will resolve with the final merged data after the last multipart chunk has arrived in the response.v3.7.2
Compare Source
Patch Changes
Only show dev tools suggestion in the console when
connectToDevTools
istrue
.@chris110408 in #10258
Pass
TCache
generic toMutationHookOptions
for better type support inuseMutation
.@igrlk in #10223
Add
name
property toApolloError
to ensure better type safety and help error reporting tools better identify the error.@aaronadamsCA in #9323
Export a
ModifierDetails
type for thedetails
parameter of aModifier
function.@KeithGillette in #7133
Revert use of
cloneDeep
to clone options when fetching queries.@MrDoomBringer in #10215
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.