Clarify mutation fetchPolicy
options using MutationFetchPolicy
union type
#8602
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.
These are the changes I was suggesting in my comments on PR #8595:
fetchPolicy
option ofuseMutation
#8595 (review)I believe this addition of
MutationFetchPolicy
is a backwards-compatible change, since it amounts to replacing a type that could only be"no-cache" | undefined
with a strictly additive superset:"network-only" | "no-cache" | undefined
.I don't expect anyone to want/need to pass
fetchPolicy: "network-only"
explicitly, but I think it makes sense to be explicit about the default mutationfetchPolicy
behavior, and its relationship to the"no-cache"
alternative.