feat(query-core): add MutationFunctionContext argument to mutateFn #9193
+51
−3
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.
This PR adds new argument to
mutateFn
allowing for access toqueryClient
as well asmeta
object.This feature should make it easier to attach authentication headers from within
mutateFn
, that would typically live inQueryCache
. Currently that's made very difficult and requires either having singleton context in the codebase or requiring consumers of mutations to pass auth token each time.This PR also makes it more similar to how
queryFn
behaves, in that it acceptsQueryFunctionContext
.Note: I wasn't entirely sure about the name of
MutateFunctionContext
, but ultimately I decided to go ahead with that name to mirror the wayqueryFn
behaves. I realise this might be suboptimal, due to there already existing aTContext
for mutations. Happy to discuss and take direction here.