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
OpenAPI 3.1 #1872
Comments
Security wise While in Probably we should issue a warning during Assertion should be trivial as the user can use the |
Greetings Sorry about the double ping, but this is a blocking issue at one of my pet projects. Is there any issue I could help with? |
So this will implement the required changes regarding security. After this, we still need to work the remaining changes which are more now level, like the "everything is a jsonschema now". |
All security related tasks have been merged. We shall now focus on the yaml/schema changes |
@pmlopes does this includes draft 2020-12 support? I think I could help with that. Taking a brief look, vertx json schema implementation already uses a pseudo-vocabulary for OpenAPI (I took a brief look, I could be wrong), I will further investigate and see if I can help. |
@LouizFC I don't think so. All json schema support is handled in another repo: https://github.com/eclipse-vertx/vertx-json-schema If you want to help, please checkout that code and implement a pull request for the latest spec. |
Depends (maybe) on: eclipse-vertx/vertx-json-schema#43 |
We now have support for openapi 3.1 in the new module vertx-web-openapi-router |
this is marked to be delivered in 4.4.1 and even docs say that OpenAPI 3.1 is supported, however the class
|
OpenAPI 3.1 is out, we need to support it https://www.openapis.org/blog/2021/02/16/migrating-from-openapi-3-0-to-3-1-0
The vertx-json-schema package already supports the latest json schema Draft 2019-09, so we need to just wire it up with vertx-web-openapi
The text was updated successfully, but these errors were encountered: