The highly customizable and versatile GraphQL client with which you add on features like normalized caching as you grow.
MIT License
Bot releases are hidden (Show)
next-urql
and clean up suspense warning message, by @ryan-gilb (See #603)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)cache-only
operations being forwarded and triggering fetch requests, by @JoviDeCroock (See #551)cache-only
operations being forwarded and triggering fetch requests, by @JoviDeCroock (See #551)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)maskTypename
export to urql-core, this deeply masks typenames from the given payload.__typename
properties is also available as a maskTypename
option on the Client
. Setting this to true willPublished by kitten almost 5 years ago
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.
Published by kitten almost 5 years ago
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.
Published by kitten almost 5 years ago
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.
[email protected]
with the prior fix in #496 (see #499)Published by kitten almost 5 years ago
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.
originalError
on GraphQLError
instances (see #470)stringifyVariables
not using .toJSON()
which prevented Dates from being stringified, by @BjoernRave (see #485)urql/core
without any React code included (see #424)