urql

Patch Changes

• Loosen type constraint on ScalarObject to account for custom scalar deserialization like Date for DateTimes, by @kitten (See #1648)
• Loosen the typing constraint on the cacheExchange generic, by @JoviDeCroock (See #1675)

Patch Changes

• ⚠️ Fix a condition under which the Client would hang when a query is started and consumed with toPromise(), by @kitten (See #1634)
• Refactor Client to hide some implementation details and to reduce size, by @kitten (See #1638)

Patch Changes

• ⚠️ Fix TTL being updated to a newer timestamp when a cached result comes in, and prevent TTL from being deleted on our React binding's cache probes. Instead we now never delete the TTL and update it on incoming cache miss results, by @kitten (See #1641)
• Updated dependencies (See #1634 and #1638)
  • @urql/[email protected]

Patch Changes

• ⚠️ Fix an edge-case for which an introspection query during runtime could fail when schema-awareness was enabled in Graphcache, since built-in types weren't recognised as existent, by @kitten (See #1631)

Patch Changes

• ⚠️ Fix a regression in @urql/[email protected] that prevented concurrent operations from being dispatched with differing request policies, which for instance prevented the explicit executeQuery calls on bindings to fail, by @kitten (See #1626)

Minor Changes

• Add options to @urql/introspection's minifyIntrospectionQuery allowing the inclusion of more
  information into the minified schema as needed, namely includeScalars, includeEnums,
  includeInputs, and includeDirectives, by @kitten (See #1578)

Patch Changes

• Remove closure-compiler from the build step (See #1570)

Minor Changes

• Add cache.link(...) method to Graphcache. This method may be used in updaters to update links in the cache. It is hence the writing-equivalent of cache.resolve(), which previously didn't have any equivalent as such, which meant that only cache.updateQuery or cache.writeFragment could be used, even to update simple relations, by @JoviDeCroock (See #1551)
• Add on a generic to cacheExchange and offlineExchange for future, experimental type-generation support, by @JoviDeCroock (See #1562)

Patch Changes

• ⚠️ Fix up internal types in Graphcache to improve their accuracy for catching more edge cases in its implementation. This only affects you if you previously imported any type related to ScalarObject from Graphcache which now is a more opaque type. We've also adjusted the NullArray types to be potentially nested, since lists in GraphQL can be nested arbitarily, which we were covering but didn't reflect in our types, by @kitten (See #1591)
• Remove closure-compiler from the build step (See #1570)
• ⚠️ Fix list items being returned as null even for non-nullable lists, when the entities are missing in the cache. This could happen when a resolver was added returning entities or their keys. This behaviour is now (correctly) only applied to partial results with schema awareness, by @JoviDeCroock (See #1566)
• Allow for the schema subscription and mutationType to be null, by @JoviDeCroock (See #1530)
• Updated dependencies (See #1570, #1509, #1600, and #1515)
  • @urql/[email protected]

Patch Changes

• Remove closure-compiler from the build step (See #1570)

Patch Changes

• Remove closure-compiler from the build step (See #1570)
• Updated dependencies (See #1570, #1509, #1600, and #1515)
  • @urql/[email protected]

Patch Changes

• Remove closure-compiler from the build step (See #1570)
• Updated dependencies (See #1570, #1509, #1600, and #1515)
  • @urql/[email protected]

Minor Changes

• With the "single-source behavior" the Client will now also avoid executing an operation if it's already active, has a previous result available, and is either run with the cache-first or cache-only request policies. This is similar to a "short circuiting" behavior, where unnecessary work is avoided by not issuing more operations into the exchange pipeline than expected, by @kitten (See #1600)
• Add consistent "single-source behavior" which makes the Client more forgiving when duplicate
  sources are used, which previously made it difficult to use the same operation across an app
  together with cache-and-network; This was a rare use-case, and it isn't recommended to overfetch
  data across an app, however, the new Client implementation of shared sources ensures that when an
  operation is active that the Client distributes the last known result for the active operation to
  any new usages of it (which is called “replaying stale results”) (See #1515)

Patch Changes

• Remove closure-compiler from the build step (See #1570)
• ⚠️ Fix inconsistency in generating keys for DocumentNodes, especially when using GraphQL Code Generator, which could cause SSR serialization to fail, by @zenflow (See #1509)

Patch Changes

• Remove closure-compiler from the build step (See #1570)
• Updated dependencies (See #1570, #1509, #1600, and #1515)
  • @urql/[email protected]

Patch Changes

• Remove closure-compiler from the build step (See #1570)
• Updated dependencies (See #1570, #1509, #1600, and #1515)
  • @urql/[email protected]

Patch Changes

• Remove closure-compiler from the build step (See #1570)
• Updated dependencies (See #1570, #1509, #1600, and #1515)
  • @urql/[email protected]

Patch Changes

• Remove closure-compiler from the build step (See #1570)
• Updated dependencies (See #1570, #1509, #1600, and #1515)
  • @urql/[email protected]

Minor Changes

• Allow subsequent static-pages to hydrate the cache, by @JoviDeCroock (See #1602)

Patch Changes

• Remove closure-compiler from the build step (See #1570)

Patch Changes

• Remove closure-compiler from the build step (See #1570)
• Updated dependencies (See #1570, #1509, #1600, and #1515)
  • @urql/[email protected]

Patch Changes

• Remove closure-compiler from the build step (See #1570)
• Updated dependencies (See #1570, #1509, #1600, and #1515)
  • @urql/[email protected]

Minor Changes

• A useClientHandle() function has been added. This creates a handle on which all use* hooks can be called, like await handle.useQuery(...) or await handle.useSubscription(...) which is useful for sequentially chaining hook calls in an async setup() function or preserve the right instance of a Client across lifecycle hooks, by @kitten (See #1599)

Patch Changes

• Remove closure-compiler from the build step (See #1570)
• The useClient() function will now throw a more helpful error when it's called outside of any lifecycle hooks, by @kitten (See #1599)
• Updated dependencies (See #1570, #1509, #1600, and #1515)
  • @urql/[email protected]

Patch Changes

• Remove closure-compiler from the build step (See #1570)
• Updated dependencies (See #1570, #1509, #1600, and #1515)
  • @urql/[email protected]