Currently, almost all Azure OpenAPI specifications are OpenAPI 2.0. There is no official JSON-Schema for OpenAPI 3.0. See OAI/OpenAPI-Specification#1032.
{
"swagger": "2.0",
"paths": {
"somepath/something": {
"get": {
"operationId": "someOperationId"
}
}
}
}
{
"swagger": "2.0",
"discriminator": "api-version",
"paths": {
"somepath/something": {
"get": [
{
"operationId": "someOperationId",
"parameters": {
"api-version": { "enum": ["2013-05", "2013-06"] }
}
},
{
"operationId": "someOperationId",
"parameters": {
"api-version": { "enum": ["2013-06"] }
}
}
]
}
}
}
See also JSON-Schema. Enumerated Values.
Discriminator
should have all values"discriminator": { "name": "api-version", "enum": ["2013-05", "2013-06"] }
- Should we rename
Operations
toOperationOverload
?
- GitHub project url
- accepting proposals/feedbacks
- operation example
- a webpage which can show generated files. Interactive?
- Vision/RoadMap for features