In UDF should function arguments with no default be not null e.g. someFunc(arg: UUID!)
vs someFunc(arg: UUID)
#444
Labels
triage-required
Pending triage from maintainers
Describe the bug
Currently when a function has an argument with no default, it still shows up as nullable in the introspection schema
For example:
Returns
given that this change would be from nullable to non-null and is only related to inputs, the change would be non-breaking in the API layer
The text was updated successfully, but these errors were encountered: