3 ms·
This is probably cool and useful, but there's no way to know how much of the API you're covering, right? I find that the real shortage of tools exists going th
by DidYaWipe 3y ago
This is probably cool and useful, but there's no way to know how much of the API you're covering, right?
I find that the real shortage of tools exists going the other way: from OpenAPI to code. The ecosystem has proven to be a huge disappointment there, comprising a janky collection of defective tools that still (years later) don't support version 3.1 (a critical update).
- deleted 3y ago[deleted]
- ivan888 3y agoI think going from code to OpenAPI makes a lot more sense, at least for strong typed languages. And even if not directly translated from code, at least closer to the actual code, in annotations or something. Generating the spec from code removes a step, where you simply need to update code, rather than update the spec then update the code
- simplesager 3y agoCompletely agree. Keeping the openapi spec as tightly coupled to types in code builds a single source truth from your development to your deployment