ENUM is being quirky about graphql-go

[EmperorEarth]

After talking with you and playing with your port a bit more, @neelance, I have an idea.

Without fully understanding your code, I think you are trying to enforce two rules:

• In your schema parser/packer, if an enum is nullable, then its resolver must have a pointer return, with a nil pointer translating to null value
• In your executor, if a type is custom, then it needs a non-nullable type to unmarshal

Combined with a third fact, ENUMs aren't a type in Go, means that nullable ENUMs are trapped between your rules.

My guess might be way off base or I might have explained this poorly. But perhaps it's a place to start.

(I'm assuming something like wrapping your unmarshaller with an adapter that can handle pointers and especially handle nil pointers?)

[neelance]

Hey, thanks for reporting this. Could you please try again with the latest master? I did some changes, but I'm not sure if it fully resolves this.

[EmperorEarth]

Can confirm, this has been fixed, thanks so much