OpenAPI-Specification
OpenAPI-Specification copied to clipboard
The OpenAPI Specification Repository
Port of #4007 to v3.2.0-dev
* 3.2.0 port of * #3991 * Run markdownlint after mdv on 3.1.1.md only because the older files won't pass * Part of #3596
This is the 3.2.0 port of * #4032 * #4020 Builds on and contains * #4025 * #4026
- second symbolic link `latest.json` for each schema as a media type hint to GitHub Pages - links both for "view" and "download  Preview: https://ralfhandl.github.io/OpenAPI-Specification/
## Weekly meetings happen on Thursdays at 9am - 10am Pacific This agenda gives visibility into discussion topics for the weekly Technical Developer Community (TDC) meetings. Sharing agenda items in...
Components fields name currently has this regex as restrictions: `^[a-zA-Z0-9\.\-_]+$` This was mainly discussed and agreed on in #634. I found this restriction a little too restrictive. I'd imagine that...
Hi there, I find myself using the power of `$ref` to reference external components in my API definitions, which is great as allows component reuse. But I find myself with...
It's currently not clear from the spec what `security: []` means. It's stated that it's _allowed_, but it doesn't say what it _does_. Obvious guesses are that it either authorizes...
### Suggested Enhancement Add a field called `summary` (or, alternatively, `label` or `title`) to the Tag Object. This optional field would be used as the "human readable" representation of the...
Feature request: standard file that describes what openapi features are supported by an implementation If all implementations provided a yaml or json file of what features were supported it would...