Search for a command to run...
Articles tagged with #tooling
A written style guide that nobody reads drifts within a month; a Spectral ruleset that fails the build does not. Enforce operationId conventions, tag hygiene, error shapes, versioning, and security coverage with built-in and custom rules, then run them in CI and pre-commit. Here
One OpenAPI document can render five very different doc experiences. We put a realistic OpenAPI 3.1 spec with webhooks, callbacks, polymorphic schemas, and security schemes through Swagger UI, Redoc, Scalar, Stoplight Elements, and RapiDoc, and compared try-it requests, code samp
Asking an LLM to read your whole codebase and emit OpenAPI produces fluent, non-reproducible fiction. Pure AST scanning is reproducible but goes blind on dynamic serializers. The reliable design is static analysis first, with AI filling only proven gaps a human can review.
Every AI editor now speaks MCP, but each one stores config differently, supports different transports, and has its own OAuth quirks. This is the practical comparison: where the config lives, what works over stdio vs HTTP, and the gotchas for six mainstream clients.
Postman made collections the source of truth and put them in the cloud. A newer workflow makes the OpenAPI spec the source, keeps files on disk where git can see them, and treats debugging, mocks, tests, and MCP as views over one document. Here is an honest comparison.
Stoplight Studio's desktop editor is no longer maintained, and teams are re-evaluating what an OpenAPI editor should be: a visual form, a YAML IDE, or a workspace where the spec also drives mocks, tests, and MCP. Five options compared on real work.
