Skip to content
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

feat: pass context to mutationFn #7076

Closed

Conversation

momme-rtf
Copy link

Since the onMutate function offers a place for preprocessing I'd find it helpful if not only the onError, onSuccess , ... callbacks receive the context (returned by the onMutate) as an input parameter but also the mutationFn.

Discussion

Copy link

vercel bot commented Mar 11, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
query ⬜️ Ignored (Inspect) Visit Preview Mar 13, 2024 7:31am

Copy link

codesandbox-ci bot commented Mar 11, 2024

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 14c4b98:

Sandbox Source
@tanstack/query-example-angular-basic Configuration
@tanstack/query-example-react-basic-typescript Configuration
@tanstack/query-example-solid-basic-typescript Configuration
@tanstack/query-example-svelte-basic Configuration
@tanstack/query-example-vue-basic Configuration

@TkDodo
Copy link
Collaborator

TkDodo commented Mar 11, 2024

if we think this through, when we should build something similar to the QueryFunctionContext - an object that we pass as second parameter. The return value from onMutate would just be one thing that goes there, meta could be another (same as useQuery) and someday maybe even an AbortSignal.

Naming will be weird - I would like this object to be the MutationFunctionContext, but then we'd need another word than "context" for what the onMutate function returns 🤔

@momme-rtf
Copy link
Author

Hmm interesting.. What if the return value of onMutate would just contribute to the meta prop instead of being a separate property in the MutationFunctionContext?

@TkDodo
Copy link
Collaborator

TkDodo commented Mar 12, 2024

not sure if that would be betterl. To be on par with queries, meta should be what the user defines meta to be

Copy link

nx-cloud bot commented Mar 13, 2024

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 14c4b98. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution


🟥 Failed Commands
nx affected --targets=test:format,test:sherif,test:knip,test:eslint,test:lib,test:types,test:build,build --parallel=3

Sent with 💌 from NxCloud.

@momme-rtf momme-rtf closed this by deleting the head repository Mar 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants