Repository metrics
- Stars
- (1,310 stars)
- PR merge metrics
- (PR metrics pending)
Description
Is your feature request related to a problem? Please describe. Custom scalars require marshal and unmarshal functions to tell genqlient how they work.
I already have marshal and unmarshal functions written for gqlgen. I don't want to have to write them a second time or add a layer of indirection to support both gqlgen and genqlient.
Describe the solution you'd like
I would love for genqlient to respect the interfaces prescribed by gqlgen - specifically looking for MarshalGQL / UnmarshalGQL on custom types and supporting the UnmarshalX(v interface{}) (X, error) / MarshalX(v X) graphql.Marshaler APIs.
Describe alternatives you've considered Currently, I need to write functions that satisfy both the gqlgen and genqlient interfaces, both of which call into generic functions. This is particularly annoying when dealing with scalar types built-in to gqlgen.
Additional context