-
Notifications
You must be signed in to change notification settings - Fork 9
switch to OpenAPI 3.0 #205
Copy link
Copy link
Open
Labels
brainstormingIdea for a potential new feature or adaption that still needs further discussionIdea for a potential new feature or adaption that still needs further discussionbreakingThis will introduce an incombability to previous versions. Documentation update compulsoryThis will introduce an incombability to previous versions. Documentation update compulsorypriority:lowShould be quite a far way down on the agendaShould be quite a far way down on the agenda
Milestone
Description
Metadata
Metadata
Assignees
Labels
brainstormingIdea for a potential new feature or adaption that still needs further discussionIdea for a potential new feature or adaption that still needs further discussionbreakingThis will introduce an incombability to previous versions. Documentation update compulsoryThis will introduce an incombability to previous versions. Documentation update compulsorypriority:lowShould be quite a far way down on the agendaShould be quite a far way down on the agenda
Currently, we are using OpenAPI 2.0 (aka Swagger) to define our API. The newer version OpenAPI 3.0 is released for almost 4 years now, at some point we should consider switching to the newer API definition structure. This issue is meant as reminder and open for discussions and remarks on that topic.