openapi-specification
https://github.com/oai/openapi-specification
JavaScript
The OpenAPI Specification Repository
Triage Issues!
When you volunteer to triage issues, you'll receive an email each day with a link to an open issue that needs help in this project. You'll also receive instructions on how to triage issues.
Triage Docs!
Receive a documented method or class from your favorite GitHub repos in your inbox every day. If you're really pro, receive undocumented methods or classes and supercharge your commit history.
JavaScript not yet supported45 Subscribers
Add a CodeTriage badge to openapi-specification
Help out
- Issues
- Consolidated $ref-to-Some Object feature request
- RFC 7231 has been obsoleted by RFC 9110
- remove "Optional OAuth2 security" examples
- Establish governance docs for working groups
- Use URI references for Security Requirements in 3.2
- Did we break 3.2 compatibility by removing the Path Item $ref special case?
- Support `multipart/byteranges` for 206 responses
- Support application/json-seq and similar JSON-based sequential formats
- Why does the JSON schema for 3.0 specify patternProperties for component names but allows additional properties?
- Support for `multipart/mixed` (and possibly better `multipart/*` support in general)
- Docs
- JavaScript not yet supported