Allow context option in refetchQueries
#3852
Merged
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
These changes adjust `mutate`'s `refetchQueries` option to allow queries to include a custom `context` option. This `context` will then be used when refetching the query, overridding any `context` that was previsouly set with the query, when it first ran. These changes are a continuation of #3580. They do not include automatically setting the `context` of refetched queries to say the `context` used for the parent mutation. A `context` has to be specified with each refetched query, if needed. This was done to maintain backwards compatibilty (e.g. preventing issues that might arise by all of a sudden running refetched queries with a mutation `context`, that wasn't explicitly requested).
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.
These changes adjust
mutate'srefetchQueriesoption to allow queries to include a customcontextoption. Thiscontextwill then be used when refetching the query, overriding anycontextthat was previsouly set with the query, when it first ran.These changes are a continuation of #3580. They do not include automatically setting the
contextofrefetched queries to say the
contextused for the parent mutation. Acontexthas to be specifiedwith each refetched query, if needed. This was done to maintain backwards compatibilty (e.g. preventing issues that might arise by all of a sudden running refetched queries with a mutation
context, that wasn't explicitly requested).