NSwag

we are using the nswag tolchain (https://github.com/RicoSuter/NSwag) for generating c# and typescript clients based on openapi specs generated by swashbuckle. you can tweak some details using config file too. it works quite well and even has integration in msbuild to avoid manual cli steps.

https://github.com/domaindrivendev/Swashbuckle.AspNetCore https://github.com/RicoSuter/NSwag There is no need to be facetious, solutions like these exist for many platforms and ecosystems out there. I can't possibly entertain all of them. By all means, if such similar solution does not exist for your platform, then TypeSpec could indeed be a solution for you. With best regards.

N.B. the last commit/release for Swashbuckle was Jan this year. https://github.com/RicoSuter/NSwag might be a better choice for a new project. It look much more maintained and active than Swashbuckle

Nswag leaves much to be desired. I deployed an OpenAPI server and the initial deployment partners using nswag begged us to change the API to suit an issue that was reported and nswag hadn't fixed in years. I respectfully told them to pound sand and deal with it manually or better yet be a good citizen on the ecosystem that they are using for free and contribute a patch. Last I checked they were still manually patching their codegen on each deploy. /Shrug Nswag has important issues that are many years old still in their backlog. 1.6k issues, oldest unresolved 7 years old: https://github.com/RicoSuter/NSwag/issues?q=is%3Aissue+is%3A...

NSwag does a wonderful job of generating TypeScript clients from OpenAPI specs. Definitely give it a shot before killing your current setup. https://github.com/RicoSuter/NSwag (It sucks in any OpenAPI yml, not just ones from Swashbuckle/C#)

I find it odd that you've struggled so much with generating API clients. I've generated C# and TypeScript (Angular's HttpClient and React Query) clients for my API and never had any issues with them. With that being said, I didn't use OpenAPI's Java-based code generators and rather used ones made by third-party developers such as NSwag[0] and openapi-codegen[1]. [0]: https://github.com/RicoSuter/NSwag [1]: https://github.com/fabien0102/openapi-codegen

More prosaically (and judging from the description of the org), it's likely to be something like this: https://github.com/RicoSuter/NSwag Which has 1.7k issues, some of which are open for years.

I feel a bit spammy as I just commented on a comment a bit higher with the same thing, but NSwag will do the trick for you. https://github.com/RicoSuter/NSwag Works a treat and is open-source, integrates nicely with ASP WebAPI projects. Can even generate TypeScript clients with a choice of HTTP library (axios/fetch etc.) or even an Angular based client.

I've had success with NSwag for generating both TypeScript and C# clients. Highly customisable - maybe too customisable with the config being quite complex - there's CLI & GUI tools to generate configs though. https://github.com/RicoSuter/NSwag We use the C# client generator in our public sector project and package the results up within Nuget, works a treat.

Something a bit different but I'm a huge fan of NSwag recently. https://github.com/RicoSuter/NSwag We use it on a project at work in C# and I've also been using it personally on pet projects with TypeScript. Allows you to automatically generate REST API clients based on Swagger/OpenAPI specs and is very customizable. Really nice if building out microservices and you're wanting to communicate between each other or building web apps and want to communicate with APIs. Saves a lot of time writing code to make requests and handle different status codes etc. Automatically generates all the classes/interfaces with sane naming schemes etc. Even has a GUI application to generate the configs also if you wish.

Does apimatic use the following open-source code generators or it builds a proprietary code generator from scratch? Swagger Codegen: https://github.com/swagger-api/swagger-codegen OpenAPI Generator: https://github.com/OpenAPITools/openapi-generator AutoRest: https://github.com/Azure/AutoRest NSwag: https://github.com/RicoSuter/NSwag oapi-codegen: https://github.com/deepmap/oapi-codegen go-swagger: https://github.com/go-swagger/go-swagger

I'm not sure why you need to modify your serialization or protocol to get type safety. I've been using NSwag (https://github.com/NSwag/NSwag) to generate TypeScript clients from .ASP.NET controllers and it works great. It can generate TypeScript request/response handlers, and interfaces or classes for any public facing models.

I would never write Swagger by hand; why should I when I can have it generated? We are using Swashbuckle[0] to generate Swagger for our ASP.NET Web API, which have been a great experience. We can explore and test the API in Swagger UI. I have been sprinkling a bit of hypermedia on top of this with HAL, mainly just for having links. I have never met anyone wanting to go the full HATEOAS route, but simple links can go a long wa. Swagger UI have been great for this, as HAL alone isn't really expressive enough to document what a link means. On the consumer side, I have been using NSwag[1] to generate clients with good results. [0] https://github.com/domaindrivendev/Swashbuckle [1] https://github.com/NSwag/NSwag