-
-
Notifications
You must be signed in to change notification settings - Fork 348
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
Global useQuery Configuration does not apply to POST requests #1723
Comments
See this ticket: #1162 did you try.. query: {
useQuery: true,
useMutation: false,
} |
there is my config
The |
@thulstrup can you help here? |
To clarify the situation a bit, I want to know: is it possible to generate |
My code from back then looked something like this, but the override doesn’t appear to be functioning properly.
|
OK so this is a regression bug. |
What are the steps to reproduce this issue?
What happens?
Even though
useQuery: true
is configured globally, thePOST
request generates auseMutation
instead of auseQuery
.What were you expecting to happen?
I expected the
POST
request to generateuseQuery
based on the global configuration.Any logs, error output, etc?
…
Any other comments?
When specifying the
operationId
explicitly in theorval.config.js
:I have found this #515
Is it related?
What versions are you using?
The text was updated successfully, but these errors were encountered: