Vue Query: generates code that doesn't compile for vue-query about orval HOT 4 OPEN

@pbrzosko , have you found a workaround?
I find myself in a similar situation and found out it is because the variable is not wrapped with unref

from orval.

Yeah, for now I have overwritten the formBody, If I remember correctly, to be empty just for this one endpoint I have with an error. I don't use this endpoint for now so I could do it like that.

from orval.

Ok, I found a workaround.

If you use a custom instance of Axios, the generated client uses unref correctly.

You can copy this file from samples/vue-query: https://github.com/anymaniax/orval/blob/833faeb9cc656a2ec87816479a4ebf9321edfc89/samples/vue-query/src/api/mutator/custom-instance.ts

And if you re-run the generation, for me, it fixed those variables accessed before unref is called.
Hope it helps!

from orval.

Another example:

const queryFn: QueryFunction<Awaited<ReturnType<typeof sampleEntityGetMetadata>>> = ({ signal }) => sampleEntityGetMetadata(unref(id,params), { signal, ...fetchOptions });

There are two errors here:

• unref with two parameters where it expects one
• and then that status is required in params

Seems like it should simply be:

const queryFn: QueryFunction<Awaited<ReturnType<typeof sampleEntityGetMetadata>>> = ({ signal }) => sampleEntityGetMetadata(unref(id), unref(params), { signal, ...fetchOptions });

from orval.