urql

Patch Changes

• Enable users to configure suspense flag on next-urql and clean up suspense warning message, by @ryan-gilb (See #603)
• Updated dependencies (See #607 and #601)
  • @urql/[email protected]

Patch Changes

• ⚠️ Fix commutative layer edge case when lowest-priority layer comes back earlier than others, by @kitten (See #587)
• Externalise @urql/exchange-populate from bundle, by @kitten (See #590)
• ⚠️ Fix teardown events leading to broken commutativity, by @kitten (See #588)

Patch Changes

• Remove the shared package, this will fix the types file generation for graphcache, by @JoviDeCroock (See #579)
• Updated dependencies (See #577)
  • @urql/[email protected]

Patch Changes

• Remove the shared package, this will fix the types file generation for graphcache, by @JoviDeCroock (See #579)
• Updated dependencies (See #577)
  • @urql/[email protected]

Patch Changes

• Prevent active teardowns for queries on subscriptionExchange, by @kitten (See #577)

Initial release

• Moved the populateExchange from @urql/exchange-graphcache to its own package.

Minor Changes

• Add cache.invalidate to invalidate an entity directly to remove it from the cache and all subsequent cache results, e.g. cache.invalidate({ __typename: 'Todo', id: 1 }), by @JoviDeCroock (See #566)

Patch Changes

• ⚠️ Fix cache-only operations being forwarded and triggering fetch requests, by @JoviDeCroock (See #551)
• Apply Query results in-order and commutatively even when results arrive out-of-order, by @kitten (See #565)
• Updated dependencies (See #551, #542, and #544)
  • @urql/[email protected]

Initial Alpha Release

Patch Changes

• Remove type import from internal urql package file that has been removed, by @parkerziegler (See #557)
• Ensure empty object gets returned in withUrqlClient's getInitialProps. Update next-urql examples to run in the urql monorepo, by @parkerziegler (See #563)

Patch Changes

• ⚠️ Fix cache-only operations being forwarded and triggering fetch requests, by @JoviDeCroock (See #551)
• Adds a one-tick delay to the subscriptionExchange to prevent unnecessary early tear downs, by @JoviDeCroock (See #542)
• Add enableAllOperations option to subscriptionExchange to let it handle queries and mutations as well, by @kitten (See #544)

Patch Changes

• ⚠️ Fix more concurrent-mode and strict-mode edge cases and bugs by switching to useSubscription. (See #514)
• ⚠️ Fix client-side suspense support (as minimally as possible) by altering
  the useBehaviourSubject behaviour. (See #512)
• Updated dependencies (See #533, #519, #515, #512, and #518)
  • @urql/[email protected]

Patch Changes

• Switch over to using @urql/core package (See 75323c0)
• Updated dependencies (See #533, #519, #515, #512, and #518)
  • @urql/[email protected]

Patch Changes

• Move @urql/exchange-suspense to the monorepo and switch it over to @urql/core (See 83325a9)
• Updated dependencies (See #533, #519, #515, #512, and #518)
  • @urql/[email protected]

Patch Changes

• Update the updater function type of cache.updateQuery to have a return type of DataFields so that __typename does not need to be defined, by @JoviDeCroock (See #538)
• ⚠️ Fix updates not being triggered when optimistic updates diverge from the actual result. (See #160)
• Refactor away SchemaPredicates helper to reduce bundlesize. (See #161)
• Ensure that pagination helpers don't confuse pages that have less params with a
  query that has more params. (See #156)
• Updated dependencies (See #533, #519, #515, #512, and #518)
  • @urql/[email protected]

Minor Changes

• Adds the maskTypename export to urql-core, this deeply masks typenames from the given payload.
  Masking __typename properties is also available as a maskTypename option on the Client. Setting this to true will
  strip typenames from results, by @JoviDeCroock (See #533)
• Add support for sending queries using GET instead of POST method (See #519)
• Add client.readQuery method (See #518)

Patch Changes

• ⚠️ Fix ssrExchange not serialising networkError on CombinedErrors correctly. (See #515)
• Add explicit error when creating Client without a URL in development. (See #512)

This patch fixes client-side suspense. While we wouldn't recommend its use
anymore, since suspense lends itself to prerendering instead of a loading
primitive, we'd like to ensure that suspense-mode works as expected in urql.

Also, as mentioned in v1.8.0's notes, please ensure that urql upgrades to
use wonka@^4.0.7 to avoid any issues. If your bundler or packager uses a
lower version with urql, you will see runtime errors.

• Clean up unnecessary useMemo for useCallback in hooks (see #504)
• Fix synchronous, client-side suspense and simplify toSuspenseSource helper (see #506)

This patch fixes urql relying on a quirk in older versions of wonka where
shared sources wouldn't cascade cancellations, which they now do. This meant
that when an app goes from some queries/subscriptions to having none at all,
the exchange pipeline would be stopped completely.

• Fix exchange pipeline stalling when all queries end (see #503)

This release doesn't change any major feature aspects, but comes with bugfixes
to our suspense and concurrent-mode handling. Due to an upgrade to wonka@^4.0.0
this is a minor version though.

In v1.6.0 we believed to
have solved all issues related to suspense and concurrent mode. However there were
still some remaining cases where concurrent mode behaved incorrectly. With the new
useOperator hook in [email protected] we believe
to have now fixed all issues.

The initial mount of useQuery and useSubscription will now synchronously reflect
whatever urql returns, most of the times those will be cached results. Afterwards
all subsequent updates and fetches will be scheduled cooperatively with React on
an effect.

If you're using wonka for an exchange with urql you may want to upgrade to wonka@^4.0.5 soon.
You can still use the older v3.2.2 which will work with the new version (even in the same bundle),
unless you're making use of its subscribe, make, or makeSubject exports.
A migration guide can be found in the wonka docs.

• Support concurrent mode with all edge cases fully (see #496)
• Move to [email protected] with the prior fix in #496 (see #499)

This release splits our main package into two entrypoints. Importing from urql remains
unchanged, but internally this entrypoint uses urql/core, which doesn't contain any
React-related code. If you're building framework-agnostic libraries or apps without
React, you can now use urql/core directly.

• Fix originalError on GraphQLError instances (see #470)
• Fix stringifyVariables not using .toJSON() which prevented Dates from being stringified, by @BjoernRave (see #485)
• Expose urql/core without any React code included (see #424)

• Fix suspense-mode being erroneously activated when using client.query() (see #466)