Menu

I built an offline desktop app for designing API contracts first: visual OpenAPI designer, lint rules, breaking-change diff, mock server

#backend#redditbackend#yaml#schemas#specs
Reading 0:00
15s threshold

A year ago I asked on r/OpenAPI for an offline, Stoplight-style API designer. Some of my work is on networks with no internet access, so hosted tools are out, and I didn't want to hand-write thousands of lines of YAML either. Nothing fit, so I built OpenAPI Studio , a native Windows desktop app.

What it does for the API owner:

Visual design without losing the YAML. You edit operations, parameters, responses and schemas in forms and tables, and the YAML stays in sync in a code editor alongside. Every view edits the same document, so they never disagree.

Specs split across files. It resolves ./schemas/order.yaml#/Order -style $ref s across files. Go to definition works across files, and renaming a component rewrites every $ref that points to it.

Schema modelling. A canvas like a database diagram, with $ref , allOf , oneOf and anyOf relationships drawn between schemas.

Linting.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.