Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update @urql/core 4.0.10 → 4.3.0 (minor) #369

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Apr 20, 2024

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @​urql/core (4.0.10 → 4.3.0) · Repo · Changelog

Release Notes

4.2.3 (from changelog)

Patch Changes

  • Add back our cache-outcome on the document-cache, this was behind a development flag however in our normalized cache we always add it already Submitted by @JoviDeCroock (See #3464)

4.2.2 (from changelog)

Patch Changes

  • ⚠️ Fix the default cacheExchange crashing on cache-only request policies with cache misses due to undefined results Submitted by @JoviDeCroock (See #3459)

4.2.1 (from changelog)

Patch Changes

  • ⚠️ Fix incorrect JSON stringification of objects from different JS contexts. This could lead to invalid variables being generated in the Vercel Edge runtime specifically Submitted by @SoraKumo001 (See #3453)

4.2.0 (from changelog)

Minor Changes

  • Try to parse text/plain content-type as JSON before bailing out with an error Submitted by @JoviDeCroock (See #3430)

4.1.4 (from changelog)

Patch Changes

  • Implement new @defer / @stream transport protocol spec changes Submitted by @JoviDeCroock (See #3389)
  • Support non spec-compliant error bodies, i.e. the Shopify API does return errors but as an object. Adding a check whether we are really dealing with an Array of errors enables this Submitted by @JoviDeCroock (See #3395)
  • ⚠️ Fix preferGetMethod: 'force' | 'within-url-limit' not being applied correctly by the Client Submitted by @Burbenog (See #3403)

4.1.3 (from changelog)

Patch Changes

  • ⚠️ Fix missing teardown operation handling in the ssrExchange. This could lead to duplicate network operations being executed Submitted by @kitten (See #3386)

4.1.2 (from changelog)

Patch Changes

  • Explicitly unblock 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 miss Submitted by @kitten (See #3363)

4.1.1 (from changelog)

Patch Changes

  • Add case for subscriptionExchange to handle GraphQLError[] received in the error observer callback. Note: This doesn't strictly check for the GraphQLError shape and only checks for arrays and receiving errors in the ExecutionResult on the next observer callback is preferred and recommended for transports Submitted by @kitten (See #3346)

4.1.0 (from changelog)

Minor Changes

  • Update formatDocument to output FormattedNode 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 Graphcache Submitted by @kitten (See #3317)

Patch Changes

  • Add OperationContext.optimistic flag as an internal indication on whether a mutation triggered an optimistic update in @urql/exchange-graphcache's cacheExchange Submitted by @kitten (See #3308)

4.0.11 (from changelog)

Patch Changes

  • Re-order maskTypename to apply masking earlier in the chain Submitted by @kitten (See #3298)
  • ⚠️ Fix ssrExchange not formatting query documents using formatDocument. Without this call we'd run the risk of not having __typename available on the client-side when rehydrating Submitted by @kitten (See #3288)
  • Add deprecation notice for 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)

Does any of this look wrong? Please let us know.


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Apr 20, 2024
@depfu depfu bot force-pushed the depfu/update/pnpm/@urql/core-4.3.0 branch 2 times, most recently from 08156cb to 6a33b61 Compare April 23, 2024 13:46
@depfu depfu bot force-pushed the depfu/update/pnpm/@urql/core-4.3.0 branch from 6a33b61 to eca5413 Compare August 15, 2024 14:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants