OAI OpenAPI-Specification Discussions
Discussions
-
You must be logged in to vote Proposal: Supporting Loose-Coupling in Security Schemes and Security Requirements Objects
security security: authAuthentication including overlap with authorization security: configThe mechanics of severs and structure of security-related objects -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote Are there plans to add support for global responses?
re-use: globals/defaultsDefault or global components that can be overridden in some way -
You must be logged in to vote -
You must be logged in to vote Definition of a breaking change
OAI-scope versioningdescribing versions of APIs/endpoints/operations -
You must be logged in to vote -
You must be logged in to vote 3.3: allow
metadataopenapifield to just specify MAJOR.MINOR and omit the PATCH numbertags, info, license, contact, markdown usage, etc.
