-
Notifications
You must be signed in to change notification settings - Fork 371
Closed
Description
I saw in the documentation that
Regardless whether the generic type of OptionalInput is specified as nullable or not it will always result in a nullable value in Defined class, i.e. OptionalInput will appear as nullable String in the GraphQL schema and in the wrapped value.
My question is - is this behaviour going to change to the more intuitive "if I pass a non-nullable I expect the value to also be non-nullable - i.e. to match the provided type" or are there some signifcant technical difficulties that are preventing this?
Metadata
Metadata
Assignees
Labels
No labels