Not able to create Mutation from api its GET anymore on operation level

[maapteh]

Description

We have queries from api contracts, which we override to a mutation in our orval config. Somehow the POSTS, are being changable into Query. But a query into a Mutation is not working.

output: {
  override: {
    reprint: {
      query: {
        useMutation: true,
      },
    },
    search: {
      query: {
        useQuery: true,
      },
    },

So the operation search did indeed become a query, but the operation reprint stayed a query and not a mutation.

I have no clue since which version, upgrading from v7 now to latest (breaking behaviour not mentioned in v8 migration) :(

#3323

Output client

axios

Configuration (orval.config)

8.10.0

Environment

Run the command above and paste the output here.

Expected behavior

No response

Actual behavior

No response

OpenAPI document (minimal, if applicable)

openapi: 3.0.3
info:
  title: Demo
  version: 0.0.0
paths: {}

Additional context

No response

[melloware]

@wadakatu can you speak to this? Its regarding your change for 8.10.0: #2376

[maapteh]

It should have helped if we had the regression in a test, i saw @wadakatu made some more, but the existing behavior was not in a suite (in 7.11.2 it worked, but i just upgraded to latest so not sure where it got broken precisely)?
Or are there more configs like tests/configs/react-query.config.ts?

Also our useMutator suddenly needed a overload pattern, i will look into that on Monday since its another issue but suddenly signal etc was not correctly anymore, now i had to check what gets passed first (from string to string or object), second. All i want to give as feedback is that Orval has so many options, but from the migration path it looked easy :)

[maapteh]

Thank you!