4 ms·
Nice, I'll find this useful. I reference OpenAPI specs frequently as I practice spec-driven development. The spec is my source of truth for the interface, and I
by RadiozRadioz 1y ago
Nice, I'll find this useful. I reference OpenAPI specs frequently as I practice spec-driven development. The spec is my source of truth for the interface, and I use it to generate both my client and server code. It automates all the request handling boilerplate on both sides, including validation, and provides me a typed interface regardless of which language I'm using. OpenAPI of course limits the types of endpoints you can create, but I find those limits stop you doing things that are strange/surprising. I find that creating APIs that can be expressed nicely in OpenAPI leads to APIs that have a consistent feel with few gotchas and a satisfyingly predictable developer experience.
- der_gopher 1y ago100%, also openapi specs are usually huge yaml/json files and it's very hard to navigate them.
- thegagne 1y agoWhat’s in your toolkit for server and client generation?
- RadiozRadioz 1y agoMy servers are Java, my clients are Python. I use the Spring & Python generators in https://github.com/swagger-api/swagger-codegen https://github.com/swagger-api/swagger-codegen