-
-
Notifications
You must be signed in to change notification settings - Fork 370
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
Nullable not included in type definition #36
Labels
Comments
@bluenote10 Thanks for open this issue! |
Awesome, thanks! |
js2me
added a commit
that referenced
this issue
Mar 25, 2020
feat: handle nullable option for primitive types (#36) Co-authored-by: svolkov <svolkov@everpoint.ru>
Merged
js2me
added a commit
that referenced
this issue
Mar 25, 2020
* feat: handle nullable option for primitive types (#37) feat: handle nullable option for primitive types (#36) Co-authored-by: svolkov <svolkov@everpoint.ru> * bump: up version to 1.6.2; chore: update swagger2openapi to latest (6.0.0); docs: update CHANGELOG Co-authored-by: svolkov <svolkov@everpoint.ru>
Fixed in #38 |
GraiemBell
added a commit
to GraiemBell/swagger-typescript-api
that referenced
this issue
Nov 20, 2023
* feat: handle nullable option for primitive types (#37) feat: handle nullable option for primitive types (acacode/swagger-typescript-api#36) Co-authored-by: svolkov <svolkov@everpoint.ru> * bump: up version to 1.6.2; chore: update swagger2openapi to latest (6.0.0); docs: update CHANGELOG Co-authored-by: svolkov <svolkov@everpoint.ru>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
According to this information it should be possible to define a nullable type in OpenAPI 3.0.x like this:
However this generates the following TypeScript:
I was hoping it would create:
The text was updated successfully, but these errors were encountered: