urql

Patch Changes

• Enforce atomic optimistic updates so that optimistic layers are cleared before they're reapplied. This is important for instance when an optimistic update is performed while offline and then reapplied while online, which would previously repeat the optimistic update on top of its past data changes, by @kitten (See #1080)

Patch Changes

• ⚠️ Fix optimistic updates not being allowed to be cumulative and apply on top of each other. Previously in #866 we explicitly deemed this as unsafe which isn't correct anymore given that concrete, non-optimistic updates are now never applied on top of optimistic layers, by @kitten (See #1074)

Patch Changes

• ⚠️ Fix an operation that triggers willAuthError with a truthy return value being sent off twice, by @kitten (See #1075)

Patch Changes

• Changes some internals of how selections are iterated over and remove some private exports. This will have no effect or fixes on how Graphcache functions, but may improve some minor performance characteristics of large queries, by @kitten (See #1060)

Patch Changes

• Replace void union types with undefined in OperationStore to allow nullish property access in TypeScript, by @kitten (See #1053)

Patch Changes

• ⚠️ Fix missing stale flag updates on query results, by @JoviDeCroock (See #1044)

Minor Changes

• Support passing pause to stop executing queries or subscriptions, by @kitten (See #1046)

Patch Changes

• ⚠️ Fix an issue where updated context options wouldn't cause a new query to be executed, or updates to the store would erroneously throw a debug error, by @kitten (See #1046)

Patch Changes

• ⚠️ Fix stale keeping a truthy value on a cache-and-network operation, by @JoviDeCroock (See #1032)

Patch Changes

• ⚠️ Fix inline fragments being skipped when they were missing a full type condition as per the GraphQL spec (e.g { ... { field } }), by @kitten (See #1040)

The new @urql/svelte API features the query, mutation, and subscription utilities, which are
called as part of a component's normal lifecycle and accept operationStore stores. These are
writable stores that encapsulate both a GraphQL operation's inputs and outputs (the result)!
Learn more about how to use @urql/svelte in our new API docs or starting from the Basics pages.

Major Changes

• Reimplement the @urql/svelte API, which is now marked as stable, by @kitten (See #1016)

Patch Changes

• ⚠️ Fix a case where the offlineExchange would not start processing operations after hydrating persisted data when no operations arrived in time by the time the persisted data was restored. This would be more evident in Preact and Svelte due to their internal short timings, by @kitten (See #1019)

This release moves urql from being in dependencies to peerDependencies. Please install it
explicitly, as you may have already in the past, and ensure that both urql and @urql/core are
not duplicated with either npm dedupe or npx yarn-deduplicate.

npm i --save urql
# or
yarn add urql

Major Changes

• Move the urql dependency to a peer dependency.
• Remove the automatic polyfilling of fetch since this is done automatically starting at
  Next v9.4
  If you are using a version before 9.4 you can upgrade by installing isomorphic-unfetch
  and importing it to polyfill the behavior, by @JoviDeCroock (See #1018)

Minor Changes

• Add option called neverSuspend to disable React.Suspense on next.js, by @JoviDeCroock (See #923)
• Expose initUrqlClient function so that a Client can be created manually for use in Next's newer SSR methods manually, such as getServerSideProps, by @sunpietro (See #993)

Patch Changes

• Allow client.reexecuteOperation to be called with mutations which skip the active operation minimums, by @kitten (See #1011)

Patch Changes

• ⚠️ Fix small pieces of code where polyfill-less ES5 usage was compromised. This was unlikely to have affected anyone in production as Array.prototype.find (the only usage of an ES6 method) is commonly used and polyfilled, by @kitten (See #991)
• ⚠️ Fix queries that have erroed with a NetworkError (isOfflineError) not flowing back completely through the cacheExchange.
  These queries should also now be reexecuted when the client comes back online, by @kitten (See #1011)
• Updated dependencies (See #1011)
  • @urql/[email protected]

Minor Changes

• Support interfaces and nested interfaces, by @JoviDeCroock (See #963)

Patch Changes

• Updated dependencies (See #1011)
  • @urql/[email protected]

Initial Release

Minor Changes

• Update @urql/preact implementation to match urql React implementation. Internally these changes should align behaviour and updates slightly, but outwardly no changes should be apparent apart from how some updates are scheduled, by @kitten (See #1008)

Patch Changes

• Updated dependencies (See #1011)
  • @urql/[email protected]

This release of Graphcache marks a point where we deem Offline Support as ready enough to remove all experimental warnings from it and regard it as stable enough to be used in apps together with urql and @urql/preact.

• ⚠️ Fix updaters config not working when Mutation/Subscription root names were altered.
  For instance, a Mutation named mutation_root could cause store.updates to be misread and cause a
  runtime error, by @kitten (See #984)
• ⚠️ Fix operation results being obstructed by the offlineExchange when the network request has failed due to being offline and no cache result has been issued. Instead the offlineExchange will now retry with cache-only policy, by @kitten (See #985)

Initial Release

The new @urql/storybook-addon provides utilities to create mock-ups in Storybook with urql more easily!