This repository has been archived by the owner on Apr 14, 2023. It is now read-only.
Fix query deduplication documentation #1300
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The
forceFetchoption is overridden by apollo-client based on thequeryDeduplicationoption provided in either the client initialization or the query context, and can therefore be considered an internal value.Since
forceFetchis internal, andqueryDeduplicationis the option to enable/disable the dedup logic, the docs should referencequeryDeduplicationinstead.I've also clarified a little bit about how it can be disabled globally.
These changes are in conjunction with apollographql/apollo-client#6261 (and apollographql/apollo-client#6526 for a possible v2.6 release).