Avoid extra requestBody in generated services?

[Holt59]

I am trying to migrate from openapi-typescript-codegen and I noticed that in many services, I have to add an extra layer with requestBody, i.e.

// before
const myData: MyRequestType;

MyService.someMethod(myData); // before
MyService.someMethod({requestBody: myData}); // now

Is there a way to generate services without that extra requestBody?

[mrlubos]

Hey @Holt59, if we do that, how would you handle conflicts if there's another parameter with the same name in query for example?

[ghost]

Answering my own question: I think everybody standardized on the word requestBody because that's the name used in the OpenAPI spec.

[mrlubos]

@waynebloss Yes and yes + it's called body if you use the new Fetch API client. Due to the amount of breaking changes it made sense to make it a part of that.

[ghost]

Thanks! @mrlubos

[mrlubos]

Hey, just want to close out this thread. We will not be flattening the parameters in function arguments as it adds a layer of complexity that simply isn't worth it. The current approach is faster and clearly informs the user in which part of the request will the parameter be sent