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)
Published by urql-ci about 3 years ago
Published by urql-ci about 3 years ago
Published by urql-ci about 3 years ago
ExecuteExchangeArgs
interface, by @taneba (See #1837)Published by urql-ci about 3 years ago
AuthContext
type, by @arempe93 (See #1828)Published by urql-ci about 3 years ago
mutate
to infer the result's type when a TypedDocumentNode
is passed via the usual generics, like client.mutation
for instance, by @younesmln (See #1796)Published by urql-ci about 3 years ago
Published by urql-ci about 3 years ago
variables
proxy before we send it into the client, by @JoviDeCroock (See #1810)Published by urql-ci over 3 years ago
Published by urql-ci over 3 years ago
useQuery
implementation to utilise the single-source implementation of @urql/[email protected]
. This should improve the stability of promisified useQuery()
calls and prevent operations from not being issued in some edge cases, by @kitten (See #1758)Published by urql-ci over 3 years ago
ssrExchange().restoreData()
from adding results to the exchange that have already been invalidated. This may happen when restoreData()
is called repeatedly, e.g. per page. When a prior run has already invalidated an SSR result then the result is 'migrated' to the user's cacheExchange
, which means that restoreData()
should never attempt to re-add it again, by @kitten (See #1776)stale: true
, where a cache-first
operation issued by Graphcache wouldn't yield an affected query and update its result to reflect the loading state with stale: true
. This is a regression from v2.1.0
and mostly becomes unexpected when cache.invalidate(...)
is used, by @kitten (See #1755)Published by urql-ci over 3 years ago
relayPagination
and simplePagination
helpers return value as Resolver<any, any, any>
as there's no way to match them consistently to either generated or non-generated resolver types anymore, by @kitten (See #1778)Published by urql-ci over 3 years ago
Published by urql-ci over 3 years ago
Published by urql-ci over 3 years ago
operationStore
updates when query
, variables
, and context
are changed. This also adds an operationStore(...).reexecute()
method, which optionally accepts a new context value and forces an update on the store, so that a query may reexecute, by @kitten (See #1780)subscription(...)
type further to allow any operationStore
input, regardless of the Result
produced, by @kitten (See #1779)Published by urql-ci over 3 years ago
Published by urql-ci over 3 years ago
bivarianceHack
in the graphcache
types to better support code-generated configs, by @JoviDeCroock (See #1687)Published by urql-ci over 3 years ago
Published by urql-ci over 3 years ago
OperationStore
and subscription
types to allow for result types of data
that differ from the original Data
type, which may be picked up from TypedDocumentNode
, by @kitten (See #1731)Published by urql-ci over 3 years ago
useQuery
's executeQuery
state updates, where some calls wouldn't trigger a source change and start a request when the hook was paused, by @kitten (See #1722)Published by urql-ci over 3 years ago