OperationId's as client methods

[lindeberg]

NSwag has a mode that makes OperationId the basis for client method names. It's awesome, so easy to understand what is being called. Compare these:
ApiClient.RedeemVoucherAsync("code");
ApiClient.App.V2.Vouchers["code"].Redemptions.PostAsync();

Could Kiota add this feature?

[lindeberg]

Also, these methods simplifies test doubles enormously, along with NSwag adding interfaces to the clients.

[lindeberg]

I'm worried because NSwag and Swashbuckle maintainers expresses lowered motivation from Microsoft replacing their packages, with less customizability, while there are thousands of users/companies using them and enjoying their API, and will likely have to migrate to Kiota soon.

[sebastienlevert]

Hello @lindeberg! Thanks for reaching out!

Kiota is not aiming at being a replacement of NSwag or any other OpenAPI generator. It plays a role in the ecosystem. We made architecture decisions to respect the rules of the path and think that consistency among all generated clients is a clear benefit to our users. Our architect (@darrelmiller) wrote a really interesting blog post about some of the design decisions and why we believe representing the path as a fluent API is a valuable approach for developers.

Hope this helps!