generated from TBD54566975/tbd-project-template
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Make sure schema generation handles optional properly #2356
Labels
Comments
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In general schema generation should rely on the
@NotNull
annotation to handle optional values during schema generation. If a field / param has this annotation then it is not optional, otherwise it is. There are some exceptions to this such as primitive values which can never be null.This should align with Kotlins type system, so Kotlin objects will map natively.
At the moment we don't really take this into account.
The text was updated successfully, but these errors were encountered: