urql

Minor Changes

• Introduce maxDepth and skipType into the populateExchange, these options allow you to specify
  the maximum depth a mutation should be populated as well as which types should not be counted towards
  this depth
  Submitted by @JoviDeCroock (See #3023)

Patch Changes

• Updated dependencies (See #3007, #2962, #3007, #3015, and #3022)
  • @urql/[email protected]

Patch Changes

• ⚠️ Fix type utilities turning the variables properties optional when a type from TypedDocumentNode has no Variables or all optional Variables. Previously this would break for wrappers, e.g. in code generators, or when the type didn't quite match what we'd expect
  Submitted by @kitten (See #3022)
• Updated dependencies (See #3007, #2962, #3007, #3015, and #3022)
  • @urql/[email protected]

Patch Changes

• ⚠️ Fix potential data loss in offlineExchange that's caused when onOnline triggers and flushes mutation queue before the mutation queue is used, by @trcoffman (See #2945)
• Patch message for (16) Heuristic Fragment Matching, by @inokawa (See #2923)
• Patch message for (19) Can't generate a key for invalidate(...) error, by @inokawa (See #2918)

Minor Changes

• Adds enableForMutation option for exchange-persisted-fetch to enable persisted operations for mutations, by @geekuillaume (See #2951)

Patch Changes

• Add pageProps: {} entry to props on app components, by @JoviDeCroock (See #2909)

Patch Changes

• ⚠️ Fix operation being blocked for looping due to it not cancelling the looping protection when a teardown is received. This bug could be triggered when a shared query operation triggers again and causes a cache miss (e.g. due to an error). The re-execution of the operation would then be blocked as Graphcache considered it a "reexecution loop" rather than a legitimate execution triggered by the UI. (See https://github.com/urql-graphql/urql/pull/2737 for more information), by @kitten (See #2876)

Patch Changes

• ⚠️ Fix type-generation, with a change in TS/Rollup the type generation took the paths as src and resolved them into the types dir, by @JoviDeCroock (See #2870)

Patch Changes

• Correctly mark cache-hits from the ssr-exchange, by @JoviDeCroock (See #2872)
• ⚠️ Fix type-generation, with a change in TS/Rollup the type generation took the paths as src and resolved them into the types dir, by @JoviDeCroock (See #2870)
• ⚠️ Fix regression in @urql/core's stringifyDocument that caused some formatted documents to not be reprinted, by @JoviDeCroock (See #2871)

Patch Changes

• ⚠️ Fix type-generation, with a change in TS/Rollup the type generation took the paths as src and resolved them into the types dir, by @JoviDeCroock (See #2870)
• Updated dependencies (See #2872, #2870, and #2871)
  • @urql/[email protected]

Patch Changes

• ⚠️ Fix type-generation, with a change in TS/Rollup the type generation took the paths as src and resolved them into the types dir, by @JoviDeCroock (See #2870)
• Updated dependencies (See #2872, #2870, and #2871)
  • @urql/[email protected]

Patch Changes

• ⚠️ Fix type-generation, with a change in TS/Rollup the type generation took the paths as src and resolved them into the types dir, by @JoviDeCroock (See #2870)
• Updated dependencies (See #2872, #2870, and #2871)
  • @urql/[email protected]

Patch Changes

• ⚠️ Fix type-generation, with a change in TS/Rollup the type generation took the paths as src and resolved them into the types dir, by @JoviDeCroock (See #2870)
• Updated dependencies (See #2872, #2870, and #2871)
  • @urql/[email protected]

Patch Changes

• Change import for createClient to @urql/core, which helps Next not depend on urql and hence not cause createContext to be called when the import is treeshaken away, by @SleeplessOne1917 (See #2833)

Patch Changes

• Solve issue where partial data could cause loops between related queries, by @JoviDeCroock (See #2831)
• Add skipping of garbage collection runs when the cache is waiting for optimistic, deferred or other results in layers. This means that we only take an opportunity to run garbage collection after results have settled and are hence decreasing the chance of hogging the event loop when a run isn't needed, by @kitten (See #2862)
• ⚠️ Fix a deadlock condition in Graphcache's layers, which is caused by subscriptions (or other deferred layers) starting before one-off mutation layers. This causes the mutation to not be completed, which keeps its data preferred above the deferred layer. That in turn means that layers stop squashing, which causes new results to be missing indefinitely, when they overlap, by @kitten (See #2861)
• Updated dependencies (See #2843, #2847, #2850, and #2846)
  • @urql/[email protected]

Minor Changes

• The context option, which may be set to a context value or a function returning a context, can now return a Promise and will be correctly resolved and awaited, by @YutaUra (See #2806)

Patch Changes

• End iterator when teardown functions runs, previously it waited for one extra call to next, then ended the iterator, by @danielkaxis (See #2803)
• Updated dependencies (See #2843, #2847, #2850, and #2846)
  • @urql/[email protected]

Patch Changes

• Move remaining Variables generics over from object default to Variables extends AnyVariables = AnyVariables. This has been introduced previously in #2607 but some missing ports have been missed due to TypeScript not catching them previously. Depending on your TypeScript version the object default is incompatible with AnyVariables, by @kitten (See #2843)
• Updated dependencies (See #2843, #2847, #2850, and #2846)
  • @urql/[email protected]

Minor Changes

• Implement mapExchange, which replaces errorExchange, allowing onOperation and onResult to be called to either react to or replace operations and results. For backwards compatibility, this exchange is also exported as errorExchange and supports onError, by @kitten (See #2846)

Patch Changes

• Move remaining Variables generics over from object default to Variables extends AnyVariables = AnyVariables. This has been introduced previously in #2607 but some missing ports have been missed due to TypeScript not catching them previously. Depending on your TypeScript version the object default is incompatible with AnyVariables, by @kitten (See #2843)
• Reuse output of stringifyDocument in place of repeated print. This will mean that we now prevent calling print repeatedly for identical operations and are instead only reusing the result once.
  This change has a subtle consequence of our internals. Operation keys will change due to this
  refactor and we will no longer sanitise strip newlines from queries that @urql/core has printed, by @kitten (See #2847)
• Update to wonka@^6.1.2 to fix memory leak in fetch caused in Node.js by a lack of clean up after initiating a request, by @kitten (See #2850)

Patch Changes

• Move remaining Variables generics over from object default to Variables extends AnyVariables = AnyVariables. This has been introduced previously in #2607 but some missing ports have been missed due to TypeScript not catching them previously. Depending on your TypeScript version the object default is incompatible with AnyVariables, by @kitten (See #2843)
• Updated dependencies (See #2843, #2847, #2850, and #2846)
  • @urql/[email protected]

Patch Changes

• Set operations when updating the cache with a result, by @JoviDeCroock (See #2782)

Patch Changes

• Ensure we aren't eagerly removing layers that are caused by subscriptions, by @JoviDeCroock (See #2771)