fix(deps): update dependency @urql/core to v4.3.0 #42
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.10
->4.3.0
Release Notes
urql-graphql/urql (@urql/core)
v4.3.0
Compare Source
Minor Changes
multipart/mixed
responses (result properties essentially are namespaced on apayload
key)Submitted by @JoviDeCroock (See #3499)
DocumentNode
with no/empty definitions and adocumentId
property is considered a persisted document. When this is detected adocumentId
parameter rather than aquery
string is sent to the GraphQL API, similar to Automatic Persisted Queries (APQs). However, APQs are only supported via@urql/exchange-persisted
, while support fordocumentId
is now built-inSubmitted by @kitten (See #3515)
Patch Changes
url
to be a plain, non-URL pathname (i.e./api/graphql
) to be used withpreferGetMethod
Submitted by @akrantz01 (See #3514)
Headers
class being used infetchOptions
Submitted by @JoviDeCroock (See #3505)
v4.2.3
Compare Source
Patch Changes
Submitted by @JoviDeCroock (See #3464)
v4.2.2
Compare Source
Patch Changes
cacheExchange
crashing oncache-only
request policies with cache misses due toundefined
resultsSubmitted by @JoviDeCroock (See #3459)
v4.2.1
Compare Source
Patch Changes
Submitted by @SoraKumo001 (See #3453)
v4.2.0
Compare Source
Minor Changes
text/plain
content-type as JSON before bailing out with an errorSubmitted by @JoviDeCroock (See #3430)
v4.1.4
Compare Source
Patch Changes
@defer
/@stream
transport protocol spec changesSubmitted by @JoviDeCroock (See #3389)
errors
but 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 theClient
Submitted by @Burbenog (See #3403)
v4.1.3
Compare Source
Patch Changes
teardown
operation handling in thessrExchange
. This could lead to duplicate network operations being executedSubmitted by @kitten (See #3386)
v4.1.2
Compare Source
Patch Changes
client.reexecuteOperation
calls to allow stalled operations from continuing and re-executing. Previously, this could cause@urql/exchange-graphcache
to stall if an optimistic mutation led to a cache missSubmitted by @kitten (See #3363)
v4.1.1
Compare Source
Patch Changes
subscriptionExchange
to handleGraphQLError[]
received in theerror
observer callback.Note: This doesn't strictly check for the
GraphQLError
shape and only checks for arrays and receiving errors in theExecutionResult
on thenext
observer callback is preferred and recommended for transportsSubmitted by @kitten (See #3346)
v4.1.0
Compare Source
Minor Changes
formatDocument
to outputFormattedNode
type mapping. The formatter will now annotate added__typename
fields with_generated: true
, place selection nodes' directives onto a_directives
dictionary, 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.optimistic
flag as an internal indication on whether a mutation triggered an optimistic update in@urql/exchange-graphcache
'scacheExchange
Submitted by @kitten (See #3308)
v4.0.11
Compare Source
Patch Changes
maskTypename
to apply masking earlier in the chainSubmitted by @kitten (See #3298)
ssrExchange
not formatting query documents usingformatDocument
. Without this call we'd run the risk of not having__typename
available on the client-side when rehydratingSubmitted by @kitten (See #3288)
maskTypename
option.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)
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.
This PR was generated by Mend Renovate. View the repository job log.