AutoRest is one of those buggy generators that I mentioned.
I agree that generated clients are ugly which is one reason why I'm hesitant. On the other hand, generators saves time and doesn't need to be tested (If you can trust the generator).
The other option that I'm thinking of is to create my own template for one of those OpenAPI generator so that the client code isn't ugly but creating a template is not a trivial task.
I'm wondering companies that has tons of REST microservices do it.
I don't have tones of micros but dozens of pretty big backends. I create all in PowerShell which is epic as it isn't compiled so you can ad hoc change it while you still have serious dev tools to do that. I am not talking only about 1 to 1 interface either, but little conveniences here and there too that are in the language or domain sprit.
I looked once into making it automatic but didn't make anything of it at that moment. While I appreciate the option and there is certainly a context where it can apply, I didn't use it so far myself.
Microservices should really have only a couple of APIs to be micro. Yeah, there are tones of them but it should be in the job description of the maker to implement client too, and do service automatic tests using it.
I agree that generated clients are ugly which is one reason why I'm hesitant. On the other hand, generators saves time and doesn't need to be tested (If you can trust the generator).
The other option that I'm thinking of is to create my own template for one of those OpenAPI generator so that the client code isn't ugly but creating a template is not a trivial task.
I'm wondering companies that has tons of REST microservices do it.