We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What you were expecting:
In v3.19.x I used to be able to await updateMany() using the returnPromise: true mutationOption.
await updateMany()
returnPromise: true
What happened instead:
Does not work in v4.x. However it's still available with useUpdate().
useUpdate()
If this change is intended could you outline in the migration docs how to mitigate this breaking change?
Related code:
const [updateMany, { data }] = useUpdateMany() const onSubmit = async () => { await updateMany('posts', { ids: [1, 2], data: { ... } }, { mutationMode: 'pessimistic', returnPromise: true }) }
The text was updated successfully, but these errors were encountered:
Thanks for the report. You're right, the returnPromise option isn't implemented in updateMany. I'm marking it as a bug.
returnPromise
updateMany
Sorry, something went wrong.
useUpdateMany
Successfully merging a pull request may close this issue.
What you were expecting:
In v3.19.x I used to be able to
await updateMany()
using thereturnPromise: true
mutationOption.What happened instead:
Does not work in v4.x. However it's still available with
useUpdate()
.If this change is intended could you outline in the migration docs how to mitigate this breaking change?
Steps to reproduce:
Related code:
The text was updated successfully, but these errors were encountered: