-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Fix fetchMore
for queries with no-cache
fetch policies
#11974
Conversation
🦋 Changeset detectedLatest commit: aca0f10 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
size-limit report 📦
|
✅ Deploy Preview for apollo-client-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
fetchMore
for queries with no-cache
fetch policies
4760823
to
87d23cb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good, but also some questions seem more prevalent with no-cache
than they seem with a cache. Do we have good answers for those?
Fixes #11965
This fixes several issues when using
fetchMore
withno-cache
queries.fetchMore
result to the cacheupdateQuery
function.Important
This PR updates
fetchMore
to force the user to provide anupdateQuery
function when using a query with ano-cache
fetch policy. Without this, there is no way for the user to determine how to merge the result with the current query data since other mechanisms rely on the cache to perform this functionality. CallingfetchMore
without anupdateQuery
function will now throw.