Nullable interface lists are not idiomatic

[ssttevee]

Returning a list of nullable interface types generates a signature that is not idiomatic and is hard to work with.

Expected Behaviour

type Interface interface {
	IsInterface()
}

type QueryResolver interface {
	List(ctx context.Context) ([]Interface, error)
}

Actual Behavior

type Interface interface {
	IsInterface()
}

type QueryResolver interface {
	List(ctx context.Context) ([]*Interface, error)
}

Minimal graphql.schema and models to reproduce

interface Interface {}

type Query {
    list: [Interface]!
}

[JamWils]

You're missing an extra exclamation point.

list: [Interface!]!

This is GraphQL saying I want a type of Interface that is not nullable within an array that is not nullable. The generator will generate the correct code at that point.

[ssttevee]

You're not wrong, but what I want is a non-nullable array of nullable values of that interface type.

[gavbaa]

Per your example, isn't that exactly what you're getting currently?

List(ctx context.Context) ([]*Interface, error)

The array itself is non-nullable (it's just a slice), of nullable values (*Interface). How would Interface be nullable in your expected behavior?

[vektah]

The array itself is non-nullable (it's just a slice), of nullable values (*Interface). How would Interface be nullable in your expected behavior?

Both slices and interfaces act like pointers, and can be assigned nil without needing to be pointers.