If you're familiar with OpenAPI you're probably familiar with "Bundling", also known by some as "Resolving" or "Dereferencing", "External Inlining"... there's a lot of names for this, but basically we are talking about pulling all the referenced parts of OpenAPI documents (linked together using $ref) into a single OpenAPI document.
OpenAPI v3.1.0 has a bunch of great changes, solving problems like the subtle differences between JSON Schema objects and OpenAPI Schema objects, and adds support for Webhooks. Upgrading tooling can be tricky, but this should be a lot easier than the jump from v2 to v3.0. To
Two months ago I teased that Stoplight was about to release something big, and yesterday we announced Stoplight Studio - an OpenAPI and standalone JSON Schema editor, which just so happens to be visually stunning and completely free. Studio runs as a web app or desktop app, can work with
Back in October I wrote Chasing the Perfect API Specification Workflow, which was a huge article about the state of the API specification world. One person trying to figure out a good workflow, in a sea of alternative specifications, with incomplete tooling, making it hard to see a solution for
Documentation is a nice thing to have, but it is often treated as optional or superfluous, especially in teams where the clients and servers are managed by the same people. Here the code is considered the contract, so why define it again in documentation? Certainly, with all the tooling around,