Return null if invalid enum is encountered
Describe your PR and link to any relevant issues.
In the current scenario, invalid enums are propagated to the client. This PR sends a null instead - while the graphql spec insists on returning a type error, I found this to be less breaking.
I have:
Hi @StevenACoffman (Sorry if I tagged the wrong person) and gqlgen team, Wanted to gather information / comments on this topic, before I do full on implementation.
Hey, so breaking compatibility with the GraphQL spec is not something most people will want, so I would want to only enable this behavior with a config option and have it default to off.
That said, I'm not sure it is even a common enough desire to add this PR.