-
-
Notifications
You must be signed in to change notification settings - Fork 347
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
useMutation still appears #1162
Comments
Providing a runnable reproducer would be ideal. |
I have the same problem.
v6.16.0 introduced useMutation options so I guess the problem is somehow related to that. |
I did a bit more investigation. This configuration generates both a mutation and a query function:
This only generates a query function:
|
it must be a bug in this logic here... const isMutation =
(verb !== Verbs.GET && override.query.useMutation) ||
operationQueryOptions?.useMutation; |
That did the trick for me 👍 |
Oh you tested my PR? |
Yes, I did. |
Awesome it will be in 6.0.25 |
Thank you for the quick fix! |
What are the steps to reproduce this issue?
Cannot redeclare block-scoped variable
What happens?
UseMutation remains in code despite useMutation: false for this operation Id
What were you expecting to happen?
…
Any logs, error output, etc?
config:
Any other comments?
…
What versions are you using?
6.23.0
The text was updated successfully, but these errors were encountered: