Skip to content

OptionalInput non-nullable generic #1770

@Sachanski

Description

@Sachanski

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

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions