Pull requests: OAI/OpenAPI-Specification
Author
Label
Projects
Milestones
Reviews
Assignee
Sort
Pull requests list
Clarify Link Obj parameters as best we can (3.0.4)
clarification
requests to clarify, but not change, part of the spec
links
Clarify resolving implicit connections (3.1.1)
clarification
requests to clarify, but not change, part of the spec
discriminator
re-use: globals/defaults
Default or global components that can be overridden in some way
re-use: ref/id resolution
how $ref, operationId, or anything else is resolved
security: config
The mechanics of severs and structure of security-related objects
Clarify discriminator + oneOf/anyOf/allOf usage (3.0.4)
clarification
requests to clarify, but not change, part of the spec
discriminator
Allow URI-references for Security Requiements (3.2.0)
enhancement
re-use: ref/id resolution
how $ref, operationId, or anything else is resolved
re-use: ref-everywhere
Requests to support referencing in more / all places
security: config
The mechanics of severs and structure of security-related objects
Clarify entry/complete document terminology (3.0.4)
clarification
requests to clarify, but not change, part of the spec
Appendix on RFC6570-derived behavior (3.0.4)
clarification
requests to clarify, but not change, part of the spec
param serialization
Issues related to parameter and/or header serialization
3.2.0 upport of #3801 and #2644: case insensitivity of auth scheme
security: auth
Authentication including overlap with authorization
3.1.1 upport of #3801: Link for case insensitivity of auth scheme
security: auth
Authentication including overlap with authorization
Clarify allowEmptyValue -> disregard empty values (3.0.4)
clarification
requests to clarify, but not change, part of the spec
param serialization
Issues related to parameter and/or header serialization
Preliminary review - conformance to RFC9110
Housekeeping
http
Supporting HTTP features and interactions
Clarify interoperable parsing expectations (3.0.4 port of #3732)
clarification
requests to clarify, but not change, part of the spec
re-use: ref/id resolution
how $ref, operationId, or anything else is resolved
Support streaming JSON formats such as json-seq
enhancement
media and encoding
Issues regarding media type support and how to encode data (outside of query/path params)
$ref objects are legal in all path-item objects
Schema
#3676
opened Mar 23, 2024 by
karenetheridge
•
Draft
ProTip!
no:milestone will show everything without a milestone.