Releases: urql-graphql/urql-exchange-graphcache
v1.0.0
Note: The minimum required version of
urql
for this release is now1.5.1
!
Hooray it's v1.0.0
time! This doesn't mean that we won't be changing little things anymore, but we're so far happy with our API and trust Graphcache to work correctly. We will further iterate on this version with some planned features, like "fragment invalidation", garbage collection, and more.
This version refactors the cache resolvers and adds some new special powers to them! You can now return almost anything from cache resolvers and trust that it'll do the right thing:
- You can return entity keys, which will resolve the cached entities
- You can return keyable entities, which will also be resolved from cache
- You may also return unkeyable entities, which will be partially resolved from cache, with your resolved values taking precedence
This can also be nested, so that unkeyable entities can eventually lead back to normal, cached entities!
This has enabled us to expose the relayPagination()
helper! This is a resolver that you can just drop into the cacheExchange
's resolvers
config. It automatically does Relay-style pagination, which is now possible due to our more powerful resolvers! You can import it from @urql/exchange-graphcache/extras
.
1.0.0-rc.11
1.0.0-rc.10
- ⚠ Fix removing cache entries by upgrading to Pessimism
1.1.4
(see ae72d3)
1.0.0-rc.9
- ⚠ Fix optimistic updates by upgrading to Pessimism
1.1.3
(see #81)
v1.0.0-rc.8
v1.0.0-rc.7
- ⚠ Fix reexecuted operations due to dependencies not using
cache-first
(see 0bd58f6)
v1.0.0-rc.6
v1.0.0-rc.5
- ⚠ Fix user-provided
keys
config not being able to returnnull
(see #68)
v1.0.0-rc.4
- ⚠ Fix development warnings throwing an error for root fields (see #65)
v1.0.0-rc.3
Note: This is release contains a bug that v1.0.0-rc.4
fixes
- Fix warning condition for missing entity keys (see 98287ae)