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

[Client] Use openapi-generator instead of swagger #3871

Closed
Bobgy opened this issue May 29, 2020 · 2 comments · Fixed by #3872
Closed

[Client] Use openapi-generator instead of swagger #3871

Bobgy opened this issue May 29, 2020 · 2 comments · Fixed by #3872
Assignees
@Bobgy
Labels
area/api area/sdk/client kind/misc types beside feature and bug priority/p0 status/triaged Whether the issue has been explicitly triaged

Comments

@Bobgy
Copy link
Contributor

Bobgy commented May 29, 2020 •
edited
Loading

This topic arises from #3216 and #3764.

Especially, #3764 makes me think we should do the switch right now.

openapi-generator seems more maintained than swagger v2 now. It was a fork from swagger v2, so I don't expect many breaking changes, it should mostly be progressive improvements.

References:
@Bobgy
Copy link
Contributor Author

Bobgy commented May 29, 2020

/cc @Ark-kun @IronPan
/assign @Bobgy
I'll investigate the switch.

@Bobgy
Copy link
Contributor Author

Bobgy commented May 29, 2020

/cc @jingzhang36

@Bobgy Bobgy added kind/misc types beside feature and bug area/api priority/p0 status/triaged Whether the issue has been explicitly triaged labels May 29, 2020
@Bobgy Bobgy mentioned this issue May 29, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Bobgy Bobgy

Labels
area/api area/sdk/client kind/misc types beside feature and bug priority/p0 status/triaged Whether the issue has been explicitly triaged
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Python Client] Use openapi generator instead of swagger Bobgy/pipelines
1 participant
@Bobgy