Skip to content

OpenAPI 3.1 to Swagger 2.0 conversion #1610

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.

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

Closed
Swimburger opened this issue Apr 2, 2024 · 4 comments
Closed

OpenAPI 3.1 to Swagger 2.0 conversion #1610

Swimburger opened this issue Apr 2, 2024 · 4 comments
Labels
type:question An issue that's a question

Comments

@Swimburger
Copy link

Swimburger commented Apr 2, 2024

I could deduce that in the upcoming version, we will be able to convert OpenAPI 3 specs to 2, but didn't specifically see 3.1.
Will 3.1 to 2.0 be possible? Obviously, some things can't be converted from 3 to 2, but that's acceptable for my use case.

Context: We have a very detailed 3.1 spec and want to use it to develop a custom connector for Logic Apps/Power Automate.
Unfortunately, the custom connector editor only accepts Swagger 2.0.

@MaggieKimani1
Copy link
Contributor

Hi @Swimburger,
We're working on release a V2 that will support 3.1 -> 2.0 downcasting.

@MaggieKimani1 MaggieKimani1 added the type:question An issue that's a question label Jun 3, 2024
@JedWe
Copy link

JedWe commented Jun 24, 2024

@MaggieKimani1 any timeline when this will be available?

@MaggieKimani1
Copy link
Contributor

Hi @JedWe,
Please refer to the ongoing conversation here: #795

@baywet
Copy link
Member

baywet commented Jul 31, 2024

closing as duplicate

@baywet baywet closed this as not planned Won't fix, can't repro, duplicate, stale Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:question An issue that's a question
Projects
None yet
Development

No branches or pull requests

4 participants