-
Notifications
You must be signed in to change notification settings - Fork 133
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
Which OpenAPI version(s) is officially supported? #1647
Comments
We support the versions of swagger and openapi that are recognized by the underlying parser, we have no direct control over that ourselves.
Possibly, but even if the feature you're looking for has been added to the parser, someone would need to add that feature to guardrail itself. The goal of this project is to have more consistent codegen based on ASTs, but that doesn't give us anything for free from the openapi-codegen libraries. Does this answer your question? What was it that you were looking for? Did you try something and find it not working as you expected? |
It kinda does, thanks.
I'm trying to upgrade an openapi 3.0 doc for an API to 3.1, because i wanted to make use of a new feature:
My existing 3.0 doc works fine with guardrail, but when i tried to bump to 3.1, code-generation is failing. |
But in case you're wondering:
which corresponds to this in the doc: {
"components": {
"schemas": {
"AccountToken": {
"description": "A JWT access token for your account.",
"format": "jwt",
"type": "string",
"x-scala-type": "String"
}
}
}
} Built using the latest version of the sbt plugin (0.75.1) |
I can't find the openapi version guardrail is targeting in the docs.
(I suggest displaying this info on the docs front page, or similar)
is version
3.1.0
supported?The text was updated successfully, but these errors were encountered: