We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The JSON Schema spec supports multiple values for types which allows a property to be nullable. e.g.
type: object properties: foo: type: [string, "null"]
When generating types with this openapi-codegen it results in a void type.
export type Thing = { foo?: void; }
I realise this is differnt from OAS 3.0 where there was a separate nullable property. Does this lib support OAS 3.1?
Reference to the nullable support in OAS 3.1 OAI/OpenAPI-Specification#2244 (comment)
The text was updated successfully, but these errors were encountered:
Hi
Did you find a workaround for this ?
Thx
Sorry, something went wrong.
Indeed, we are not supporting OAS 3.1 (I was not expecting such a breaking change between 3.0 and 3.1…)
I need to document myself a bit more about what changes to see if we can support everything
For future ref -> https://www.openapis.org/blog/2021/02/16/migrating-from-openapi-3-0-to-3-1-0
No branches or pull requests
The JSON Schema spec supports multiple values for types which allows a property to be nullable.
e.g.
When generating types with this openapi-codegen it results in a void type.
I realise this is differnt from OAS 3.0 where there was a separate nullable property. Does this lib support OAS 3.1?
Reference to the nullable support in OAS 3.1
OAI/OpenAPI-Specification#2244 (comment)
The text was updated successfully, but these errors were encountered: