Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@urql/[email protected]
Minor Changes
cache.link(...)
method to Graphcache. This method may be used in updaters to update links in the cache. It is hence the writing-equivalent ofcache.resolve()
, which previously didn't have any equivalent as such, which meant that onlycache.updateQuery
orcache.writeFragment
could be used, even to update simple relations, by @JoviDeCroock (See #1551)cacheExchange
andofflineExchange
for future, experimental type-generation support, by @JoviDeCroock (See #1562)Patch Changes
ScalarObject
from Graphcache which now is a more opaque type. We've also adjusted theNullArray
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)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)@urql/[email protected]
Minor Changes
Client
will now also avoid executing an operation if it's already active, has a previous result available, and is either run with thecache-first
orcache-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)Client
more forgiving when duplicatesources 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 overfetchdata across an app, however, the new
Client
implementation of shared sources ensures that when anoperation is active that the
Client
distributes the last known result for the active operation toany new usages of it (which is called “replaying stale results”) (See #1515)
Patch Changes
DocumentNode
s, especially when using GraphQL Code Generator, which could cause SSR serialization to fail, by @zenflow (See #1509)@urql/[email protected]
Minor Changes
@urql/introspection
'sminifyIntrospectionQuery
allowing the inclusion of moreinformation into the minified schema as needed, namely
includeScalars
,includeEnums
,includeInputs
, andincludeDirectives
, by @kitten (See #1578)Patch Changes
[email protected]
Minor Changes
Patch Changes
@urql/[email protected]
Minor Changes
useClientHandle()
function has been added. This creates ahandle
on which alluse*
hooks can be called, likeawait handle.useQuery(...)
orawait handle.useSubscription(...)
which is useful for sequentially chaining hook calls in anasync setup()
function or preserve the right instance of aClient
across lifecycle hooks, by @kitten (See #1599)Patch Changes
useClient()
function will now throw a more helpful error when it's called outside of any lifecycle hooks, by @kitten (See #1599)@urql/[email protected]
Patch Changes
@urql/[email protected]
Patch Changes
@urql/[email protected]
Patch Changes
@urql/[email protected]
Patch Changes
@urql/[email protected]
Patch Changes
@urql/[email protected]
Patch Changes
@urql/[email protected]
Patch Changes
@urql/[email protected]
Patch Changes
@urql/[email protected]
Patch Changes
[email protected]
Patch Changes
@urql/[email protected]
Patch Changes
@urql/[email protected]
Patch Changes