urql

Patch Changes

• ⚠️ Fix in edge-case in client-side React Suspense, where after suspending due to an update a new state value is given to useSource in a render update. This was previously then causing us to subscribe to an outdated source in useEffect since the updated source would be ignored by the time we reach useEffect in useSource, by @kitten (See #1157)

Initial release

Patch Changes

• Add missing optional dependency (@urql/devtools), by @andyrichardson (See #1129)

Patch Changes

• ⚠️ Fix regression in client-side Suspense behaviour. This has been fixed in [email protected] and @urql/[email protected] but regressed in the patches afterwards that were aimed at fixing server-side Suspense, by @kitten (See #1142)

Patch Changes

• ⚠️ Fix regression in client-side Suspense behaviour. This has been fixed in [email protected] and @urql/[email protected] but regressed in the patches afterwards that were aimed at fixing server-side Suspense, by @kitten (See #1142)

Patch Changes

• ⚠️ Fix server-side rendering by disabling the new Suspense cache on the server-side and clear it for prepasses, by @JoviDeCroock (See #1138)
• Updated dependencies (See #1135)
  • @urql/[email protected]

Patch Changes

• Export getOperationName from @urql/core and use it in @urql/exchange-execute, fixing several imports, by @JoviDeCroock (See #1135)

Patch Changes

• Export getOperationName from @urql/core and use it in @urql/exchange-execute, fixing several imports, by @JoviDeCroock (See #1135)
• Updated dependencies (See #1135)
  • @urql/[email protected]

Patch Changes

• ⚠️ Fix server-side rendering by disabling the new Suspense cache on the server-side and clear it for prepasses, by @JoviDeCroock (See #1138)
• Updated dependencies (See #1135)
  • @urql/[email protected]

Minor Changes

• Add a second Operation input argument to the retryIf predicate, so that retrying can be actively avoided for specific types of operations, e.g. mutations or subscriptions, in certain user-defined cases, by @kitten (See #1117)

Patch Changes

• Updated dependencies (See #1119, #1113, #1104, and #1123)
  • @urql/[email protected]

Minor Changes

• Improve the Suspense implementation, which fixes edge-cases when Suspense is used with subscriptions, partially disabled, or used on the client-side. It has now been ensured that client-side suspense functions without the deprecated suspenseExchange and uncached results are loaded consistently. As part of this work, the Client itself does now never throw Suspense promises anymore, which is functionality that either way has no place outside of the React/Preact bindings, by @kitten (See #1123)

Patch Changes

• Add support for TypedDocumentNode to infer the type of the OperationResult and Operation for all methods, functions, and hooks that either directly or indirectly accept a DocumentNode. See graphql-typed-document-node and the corresponding blog post for more information., by @kitten (See #1113)
• Refactor useSource hooks which powers useQuery and useSubscription to improve various edge case behaviour. This will not change the behaviour of these hooks dramatically but avoid unnecessary state updates when any updates are obviously equivalent and the hook will furthermore improve continuation from mount to effects, which will fix cases where the state between the mounting and effect phase may slightly change, by @kitten (See #1104)
• Updated dependencies (See #1119, #1113, #1104, and #1123)
  • @urql/[email protected]

Patch Changes

• • Add @urql/devtools to @urql/storybook-addon. Previously it was not included (See #1092), but now the exchange works out of the box with Storybook, by @r281GQ (See #1112)

Minor Changes

• Improve the Suspense implementation, which fixes edge-cases when Suspense is used with subscriptions, partially disabled, or used on the client-side. It has now been ensured that client-side suspense functions without the deprecated suspenseExchange and uncached results are loaded consistently. As part of this work, the Client itself does now never throw Suspense promises anymore, which is functionality that either way has no place outside of the React/Preact bindings, by @kitten (See #1123)

Patch Changes

• Add support for TypedDocumentNode to infer the type of the OperationResult and Operation for all methods, functions, and hooks that either directly or indirectly accept a DocumentNode. See graphql-typed-document-node and the corresponding blog post for more information., by @kitten (See #1113)
• Refactor useSource hooks which powers useQuery and useSubscription to improve various edge case behaviour. This will not change the behaviour of these hooks dramatically but avoid unnecessary state updates when any updates are obviously equivalent and the hook will furthermore improve continuation from mount to effects, which will fix cases where the state between the mounting and effect phase may slightly change, by @kitten (See #1104)
• Updated dependencies (See #1119, #1113, #1104, and #1123)
  • @urql/[email protected]

Minor Changes

• Improve the Suspense implementation, which fixes edge-cases when Suspense is used with subscriptions, partially disabled, or used on the client-side. It has now been ensured that client-side suspense functions without the deprecated suspenseExchange and uncached results are loaded consistently. As part of this work, the Client itself does now never throw Suspense promises anymore, which is functionality that either way has no place outside of the React/Preact bindings, by @kitten (See #1123)

Patch Changes

• Use Record over object type for subscription operation variables. The object type is currently hard to use (see this issue), by @enisdenjo (See #1119)
• Add support for TypedDocumentNode to infer the type of the OperationResult and Operation for all methods, functions, and hooks that either directly or indirectly accept a DocumentNode. See graphql-typed-document-node and the corresponding blog post for more information., by @kitten (See #1113)
• Refactor useSource hooks which powers useQuery and useSubscription to improve various edge case behaviour. This will not change the behaviour of these hooks dramatically but avoid unnecessary state updates when any updates are obviously equivalent and the hook will furthermore improve continuation from mount to effects, which will fix cases where the state between the mounting and effect phase may slightly change, by @kitten (See #1104)

Patch Changes

• Add support for TypedDocumentNode to infer the type of the OperationResult and Operation for all methods, functions, and hooks that either directly or indirectly accept a DocumentNode. See graphql-typed-document-node and the corresponding blog post for more information., by @kitten (See #1113)
• Updated dependencies (See #1119, #1113, #1104, and #1123)
  • @urql/[email protected]

Patch Changes

• Add support for TypedDocumentNode to infer the type of the OperationResult and Operation for all methods, functions, and hooks that either directly or indirectly accept a DocumentNode. See graphql-typed-document-node and the corresponding blog post for more information., by @kitten (See #1113)
• Updated dependencies (See #1119, #1113, #1104, and #1123)
  • @urql/[email protected]

Patch Changes

• ⚠️ Fix a stray operationName deprecation warning in @urql/exchange-graphcache's exchange logic, which adds the meta.cacheOutcome field to the operation's context, by @kitten (See #1103)

Patch Changes

• ⚠️ Fix the production build overwriting the development build. Specifically in the previous release we mistakenly replaced all development bundles with production bundles. This doesn't have any direct influence on how these packages work, but prevented development warnings from being logged or full errors from being thrown, by @kitten (See #1097)
• Updated dependencies
  • [email protected]

Patch Changes

• ⚠️ Fix the production build overwriting the development build. Specifically in the previous release we mistakenly replaced all development bundles with production bundles. This doesn't have any direct influence on how these packages work, but prevented development warnings from being logged or full errors from being thrown, by @kitten (See #1097)

Patch Changes

• ⚠️ Fix the production build overwriting the development build. Specifically in the previous release we mistakenly replaced all development bundles with production bundles. This doesn't have any direct influence on how these packages work, but prevented development warnings from being logged or full errors from being thrown, by @kitten (See #1097)
• Updated dependencies (See #1097)
  • @urql/[email protected]