Override type mismatch about gqlgen

[vektah]

I haven't tested this, but you might be able to define the parent (Thing) yourself with the type you need, and point to it in your typemap.

The other way would be to define a custom scalar type for ListFooEnum, and your schema would become:

scalar CommaList
type Thing struct{
  ListOfEnums: CommaList
}

[mastercactapus]

I've ran into this as well. Certain cases make it really painful when the field names match, but have to be exposed through graphql by a different type.

A couple examples:

• struct with an ID field that is an int but needs to be a string (for graphql)
• a field is of type time.Time but it must be exposed to graphql as a string in a certain format
• a field is of a custom enum type that needs to be "mapped" (e.g. iota), but the parent struct would ideally be used directly

In cases where there is a type mismatch during code generation, it would be helpful if there was an option to behave as though there were no matching field at all (thus resolving the type mismatch with use of a resolver method).

The resolver code would then be "best-effort" where possible to auto-map fields. Anything that can't be done automatically would require a method for the Resolver interface, just like if there was no name match.

I don't feel strongly if that should be the default behavior or not though. I think a case could be made to change it, but to preserve current behavior, maybe via a flag like -ignore-type-mismatch or -skip-type-mismatch could be added. Then that flag could be set in the go:generate line where necessary.

---

Anyway I'd be happy to take a shot at this if it sounds reasonable.

[mastercactapus]

@jonlundy Now that #133 is merged, you should be able to put your mapping in a resolver for that single field (instead of getting type mismatch).