I began this PR because I encountered a bug in BindFields where the name given to a type would be the JSON field name, which resulted in conflicts. I was using that function to automatically bind functions, and create types, so that the resolver functions themselves could be reused as regular exported functions.
I migrated that code into this project as well, as I feel it offers a significant improvement to dev experience.
coverage: 91.721% (-0.3%) from 92.051% when pulling 96800046d49ef30bf2b597038f683aea7910f8ad on teamjobot:contrib into 4ebf270b92df8ca6b2eb2ed97e595e642dee9b0a on graphql-go:master.
Hello, graphql-go authors.
I began this PR because I encountered a bug in
BindFields
where the name given to a type would be the JSON field name, which resulted in conflicts. I was using that function to automatically bind functions, and create types, so that the resolver functions themselves could be reused as regular exported functions.I migrated that code into this project as well, as I feel it offers a significant improvement to dev experience.
or almost any manner of function along these lines:
or constant
Cheers!
-Alan 🤖