gotomgo

Is this not an issue of the UnmarshalGraphQL for a custom scaler type not being called? Regardless of your interpretation of JSON and int32, if I have a custom scaler...

The issue being that we are *pre* custom marshaling and dealing with very basic types (Json types), then the scanner.Int handling has to be *way* more lenient: I don't like...

Twitch updated their OAUTH and now require that a Client-ID header appear for all helix requests. So add this to the req in FetchUser: req.Header.Set("Client-ID", p.config.ClientID) See here for more...