-
-
Notifications
You must be signed in to change notification settings - Fork 454
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(graphcache) - cache.resolve(parent, ...) doesn't seem to work #1207
Comments
This probably needs a change in the documentation, but this is still working as intended. What's happened is that basically I believe the documentation sometimes speaks about using The safe method here is to use |
Thanks, @kitten I will change to |
I've discussed this with @JoviDeCroock and we came to the conclusion that this actually should be supported. We did use it ourselves in the documentation and it's a pretty intuitive way to resolve fields gradually from a parent, instead of using |
The new |
@nghiepit Nice catch! I believe I've actually forgotten to enable the additional case we were after. Follow up PR has been filed |
Hi guys,
After upgrade to
@urql/[email protected]
cache.resolve
doesn't seem to work always returnnull
value.urql: 1.11.4
@urql/exchange-graphcache: 3.3.1
Steps to reproduce
Check log tab
https://codesandbox.io/s/headless-wildflower-ynjsk
The repo older version still work
https://codesandbox.io/s/prod-monad-gmvyk
The text was updated successfully, but these errors were encountered: