-
Notifications
You must be signed in to change notification settings - Fork 5
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
compatibility for openapi 3.0.0 #33
Comments
found more issues:
it is how it looks like from woocommerce generated or
which is getting converted into |
Thanks @dpalic. I can look into 3.0 compatibility, but it will be tricky. As far as I know, WordPress supports/uses the latest JSON schema spec, which is only supported by OpenAPI 3.1.0.
I'll look into it 👍 |
if it helps I can share you a code generator via PN to identify the issues better |
That would be great! |
Hi, this tutorial may help (if new to java and maven): and afterwards
and now
|
@dpalic Thanks for the file! I'll try to reproduce the issue soon. |
Sorry for the delay. So I think we have two problems.
I can fix problem 1, but I think problem 2 is out of scope for this project. We can introduce a layer that attempts to convert the latest JSONSchema (which is supported by the latest WordPress) specification to OpenAPI 3.0, but I'm not sure how well it would work. I'll work on a fix for #1 for now. |
wanted to try #1 but i am missing an release in the meanwhile (a year ago, swagger integrated support for 3.1.0) so the generator shall do the same. So would have liked to try it |
as of checking #31 this project is built on openapi 3.1.0
the swagger generator is as of now and for unclear time not compatible to that version.
It would be great to have a compatibility mode of this wp-openapi to generate 3.0.0 openapi spec, so that many languages are out of the box supported by swagger/openapi generator
do you see any chance to support openapi 3.0.0 e.g. on a branch?
The text was updated successfully, but these errors were encountered: