@jasonkuhrt I upgraded to the latest version with the nonNullDefaults change and set both input and output to non-null, since that’s how I was using before, but the items of a list still default to nullable, is this expected behavior?

Hey @Eric Reis 👋 For lists, I think you would need to add

list: [true]

to the input options.

@matic recently hit this issue too, we're aware nullability in general is causing considerable friction for users. Thanks for raising!

imo everything non-nullable is a good enough default, do we know what it will look like in the future?

I was referring to the API

the nullablity for a list is scattered in 2 different properties,

nullable

and

list

, a typegraphql like API would be loveable, like an union type for nullable:

boolean|'list'|'list-and-item'|'item'

@jasonkuhrt

@Albert Gao feature requests welcome! The solution should account for nested lists too