Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

OpenAPI (OAS3) support #138

Open
schuderer opened this issue May 10, 2021 · 0 comments
Open

OpenAPI (OAS3) support #138

schuderer opened this issue May 10, 2021 · 0 comments
Labels
needs discussion Several opinions should be heard and considered
Projects
Prioritized User Issues

Comments

@schuderer
Copy link
Owner

Currently (as of version 1.0.0), ML Launchpad relies on RAML for specifying the API.

Are we going to support OAS3 (formerly known as Swagger) as well, and when? It seems that RAML support is becoming less crucial overall for corporate use, as MuleSoft also is starting to adopt OAS3: https://blogs.mulesoft.com/news/anypoint-platform/api-adoption-with-oas-3/

One potential issue is that OAS is really meant for bottom-up use (code driven) while ML Launchpad actually tries to keep the users away from writing API code themselves.
@schuderer schuderer added the needs discussion Several opinions should be heard and considered label May 10, 2021
@schuderer schuderer added this to To do in Prioritized User Issues via automation May 10, 2021
@schuderer schuderer mentioned this issue May 17, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs discussion Several opinions should be heard and considered
Projects
Prioritized User Issues
  
To do
Milestone
No milestone
Development

No branches or pull requests
1 participant
@schuderer