fix(deps): update dependency @urql/core to v5 #430
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
^4.0.6->^5.0.0^4.0.0->^5.0.0Release Notes
urql-graphql/urql (@urql/core)
v5.1.0Compare Source
Minor Changes
addMetadatatransform where we'd strip out metadata for production environments, this particularly affectsOperationResult.context.metadata.cacheOutcomeSubmitted by @alpavlove (See #3714)
v5.0.8Compare Source
Patch Changes
deepMergeregression on array valuesSubmitted by @JoviDeCroock (See #3696)
v5.0.7Compare Source
Patch Changes
for-ofsyntax from@urql/corehelpers for JSC memory reductionSubmitted by @kitten (See #3690)
v5.0.6Compare Source
Patch Changes
Submitted by @JoviDeCroock (See #3650)
v5.0.5Compare Source
Patch Changes
datainssrExchangeSubmitted by @negezor (See #3632)
v5.0.4Compare Source
Patch Changes
OperationKeyto take files into account, before wewould encode them to
nullresulting in every mutation with the same variables(excluding the files) to have the same key. This resulted in mutations that upload
different files at the same time to share a result in GraphCache
Submitted by @JoviDeCroock (See #3601)
v5.0.3Compare Source
Patch Changes
documentIdfrom persisted documents for document keys, when it's availableSubmitted by @kitten (See #3575)
v5.0.2Compare Source
Patch Changes
For example, this issue presents itself when Graphcache is concurrently updating multiple, inter-dependent queries with shared entities. One query completing while others are still in-flight may lead to duplicate operations being issued
Submitted by @JoviDeCroock (See #3573)
v5.0.1Compare Source
Patch Changes
@ts-ignoreon TypeScript peer dependency import in typings not being applied due to a leading!characterSubmitted by @kitten (See #3567)
v5.0.0Compare Source
Major Changes
dedupExchangeSubmitted by @JoviDeCroock (See #3520)
maskTypenameSubmitted by @JoviDeCroock (See #3520)
Patch Changes
@0no-co/graphql.webto1.0.5Submitted by @kitten (See #3553)
v4.3.0Compare Source
Minor Changes
multipart/mixedresponses (result properties essentially are namespaced on apayloadkey)Submitted by @JoviDeCroock (See #3499)
DocumentNodewith no/empty definitions and adocumentIdproperty is considered a persisted document. When this is detected adocumentIdparameter rather than aquerystring is sent to the GraphQL API, similar to Automatic Persisted Queries (APQs). However, APQs are only supported via@urql/exchange-persisted, while support fordocumentIdis now built-inSubmitted by @kitten (See #3515)
Patch Changes
urlto be a plain, non-URL pathname (i.e./api/graphql) to be used withpreferGetMethodSubmitted by @akrantz01 (See #3514)
Headersclass being used infetchOptionsSubmitted by @JoviDeCroock (See #3505)
v4.2.3Compare Source
Patch Changes
Submitted by @JoviDeCroock (See #3464)
v4.2.2Compare Source
Patch Changes
cacheExchangecrashing oncache-onlyrequest policies with cache misses due toundefinedresultsSubmitted by @JoviDeCroock (See #3459)
v4.2.1Compare Source
Patch Changes
Submitted by @SoraKumo001 (See #3453)
v4.2.0Compare Source
Minor Changes
text/plaincontent-type as JSON before bailing out with an errorSubmitted by @JoviDeCroock (See #3430)
v4.1.4Compare Source
Patch Changes
@defer/@streamtransport protocol spec changesSubmitted by @JoviDeCroock (See #3389)
errorsbut as an object. Addinga check whether we are really dealing with an Array of errors enables this
Submitted by @JoviDeCroock (See #3395)
preferGetMethod: 'force' | 'within-url-limit'not being applied correctly by theClientSubmitted by @Burbenog (See #3403)
v4.1.3Compare Source
Patch Changes
teardownoperation handling in thessrExchange. This could lead to duplicate network operations being executedSubmitted by @kitten (See #3386)
v4.1.2Compare Source
Patch Changes
client.reexecuteOperationcalls to allow stalled operations from continuing and re-executing. Previously, this could cause@urql/exchange-graphcacheto stall if an optimistic mutation led to a cache missSubmitted by @kitten (See #3363)
v4.1.1Compare Source
Patch Changes
subscriptionExchangeto handleGraphQLError[]received in theerrorobserver callback.Note: This doesn't strictly check for the
GraphQLErrorshape and only checks for arrays and receiving errors in theExecutionResulton thenextobserver callback is preferred and recommended for transportsSubmitted by @kitten (See #3346)
v4.1.0Compare Source
Minor Changes
formatDocumentto outputFormattedNodetype mapping. The formatter will now annotate added__typenamefields with_generated: true, place selection nodes' directives onto a_directivesdictionary, and will filter directives to not include"_"underscore prefixed directives in the final query. This prepares us for a feature that allows enhanced client-side directives in GraphcacheSubmitted by @kitten (See #3317)
Patch Changes
OperationContext.optimisticflag as an internal indication on whether a mutation triggered an optimistic update in@urql/exchange-graphcache'scacheExchangeSubmitted by @kitten (See #3308)
v4.0.11Compare Source
Patch Changes
maskTypenameto apply masking earlier in the chainSubmitted by @kitten (See #3298)
ssrExchangenot formatting query documents usingformatDocument. Without this call we'd run the risk of not having__typenameavailable on the client-side when rehydratingSubmitted by @kitten (See #3288)
maskTypenameoption.Masking typenames in a result is no longer recommended. It’s only
useful when multiple pre-conditions are applied and inferior to
mapping to an input object manually
Submitted by @kitten (See #3299)
v4.0.10Compare Source
Patch Changes
fetchSubscriptionsentry toOperationContext. The Client’sfetchSubscriptionsnow works properly and can be used to execute subscriptions as multipart/event-stream requestsSubmitted by @kitten (See #3244)
fetchSourcenot working for subscriptions sincehasNextisn’t necessarily setSubmitted by @kitten (See #3244)
v4.0.9Compare Source
Patch Changes
AbortControllerinvocation to previous behaviour where it used to be more forceful. It will now properly abort outside of when our generator yields results, and hence now also cancels requests again that have already delivered headers but are currently awaiting a response bodySubmitted by @kitten (See #3239)
v4.0.8Compare Source
Patch Changes
additionalTypenameson subscriptions and re-execute queries for them as well, as one would intuitively expectSubmitted by @kitten (See #3230)
Submitted by @kitten (See #3201)
isSubscriptionOperationoption insubscriptionExchangeto includeteardownoperations, to avoid confusionSubmitted by @kitten (See #3206)
v4.0.7Compare Source
Patch Changes
Submitted by @kitten (See #3180)
Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), 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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.