-
Notifications
You must be signed in to change notification settings - Fork 9k
Pull requests: OAI/OpenAPI-Specification
Author
Label
Projects
Milestones
Reviews
Assignee
Sort
Pull requests list
Improve media type serialization examples (3.0.4)
clarification
requests to clarify, but not change, part of the spec
media and encoding
Issues regarding media type support and how to encode data (outside of query/path params)
Minor webhooks/callbacks and schema requests to clarify, but not change, part of the spec
editorial
Wording and stylistic issues
examples
improvements (3.1.1)
clarification
Various minor editorial improvements (3.0.4)
clarification
requests to clarify, but not change, part of the spec
editorial
Wording and stylistic issues
example obj/keywords
Issues with the Example Object or exampel(s) keywords
http
Supporting HTTP features and interactions
metadata
tags, info, license, contact, markdown usage, etc.
Path Item $ref change warning (3.1.1)
bug
re-use: ref/id resolution
how $ref, operationId, or anything else is resolved
re-use: traits/merges
Selective or modified re-use
Appendix for percent-encoding concerns (3.0.4)
clarification
requests to clarify, but not change, part of the spec
media and encoding
Issues regarding media type support and how to encode data (outside of query/path params)
param serialization
Issues related to parameter and/or header serialization
Resolution of relative URLs in CommonMark text (3.0.4)
clarification
requests to clarify, but not change, part of the spec
metadata
tags, info, license, contact, markdown usage, etc.
re-use: ref/id resolution
how $ref, operationId, or anything else is resolved
Encoding Object content and header clarifications (3.0.4)
clarification
requests to clarify, but not change, part of the spec
media and encoding
Issues regarding media type support and how to encode data (outside of query/path params)
Alternative: Clarify resolving implicit connections (3.1.1- alternative to #3823)
clarification
requests to clarify, but not change, part of the spec
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
Clarify discriminator + oneOf/anyOf/allOf usage (3.1.1 modified port of #3822)
clarification
requests to clarify, but not change, part of the spec
discriminator
Warnings for header and cookie serialization (3.0.4)
headers
param serialization
Issues related to parameter and/or header serialization
Appendix on converting data types to strings (3.0.4)
clarification
requests to clarify, but not change, part of the spec
media and encoding
Issues regarding media type support and how to encode data (outside of query/path params)
param serialization
Issues related to parameter and/or header serialization
Clarify "URI" and "URL" meaning and usage (3.1.1)
clarification
requests to clarify, but not change, part of the spec
re-use: ref/id resolution
how $ref, operationId, or anything else is resolved
feat(spec): codify Encoding in specific requestBody mediatypes
Schema
#3837
opened May 22, 2024 by
jeremyfiel
Loading…
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
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
Allow URI-references for Security Requirements (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
Appendix on RFC6570-derived behavior + requests to clarify, but not change, part of the spec
param serialization
Issues related to parameter and/or header serialization
allowReserved
(3.0.4)
clarification
Preliminary review - conformance to RFC9110
Housekeeping
http
Supporting HTTP features and interactions
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!
Adding no:label will show everything without a label.