There is a framework in every language I've worked with that will generate the OpenAPI schema for you. That you have to sketch the API in a language is not necessarily "code-first", it's just a different language than yaml/json, (go,py,js) without the implementation, just write the same types in example
Exactly this, I’ve been a python guy which is apparently not the main language used by most api developers or what? Is there nothing like FastAPI in js land? I do start my APIs by writing the openAPI spec, only it’s written in pydantic inside FastAPI and turns out this also creates the actual API lol.
You can explicitly allow it in Site Settings, and then reload the page. For me, I click the little button (looks like sliders) to the left of the URL, Site Settings, and then scroll down to change Site Audio to "Allow".
This is the strangest debate and it's not really clear from the blog post what the benefit of picking one gets you. Why does it matter what happens on a devs branch? just do a squash and merge when merging a branch to trunk.
OpenAPI is more than just documentation generation, it’s also used for runtime time validation and codegen for both client and server stubs. I’d argue that what’s discussed in this article can complement OpenAPI but doesn’t replace it.
