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 decreased (-0.03%) to 92.344% when pulling 336c4d6d70d26396f91beb7428c1ddec2c5c9868 on teamjobot:master into 9441c498a148d34c007886e14295e13eb3efc340 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 🤖