coverage: 73.167%. remained the same
when pulling 461189d on UnAfraid:feature/reuse-arg-process-func
into a245e6f on 99designs:master.

@UnAfraid This is a massive improvement! Thank you so much!

I noticed that the only conditional template difference between the two variations is due two is whether or not it is using $useFunctionSyntaxForExecutionContext :
codegen/generated!.gotpl

What do you think about changing the name of the ExecutionContext variant and exporting both variants so they don't need to be part of the template code anymore at all?

@UnAfraid I'm going to merge this PR as it is, since it's already a huge improvement, but I would like to move as much logic out of templates as possible. If you are willing or interested in another PR to do this I would be hugely appreciative!

The code in gqlgen that is in a template receives significantly fewer contributions than the traditional library code. I believe it's primarily due to the difficulty for most developers (and tools) to understand and manipulate it.

If these functions were just exported functions in a library, we could unit test them, and they wouldn't be intimidating for any developer to help us improve. What do you think?

@UnAfraid This is a massive improvement! Thank you so much!

I noticed that the only conditional template difference between the two variations is due two is whether or not it is using $useFunctionSyntaxForExecutionContext : codegen/generated!.gotpl

What do you think about changing the name of the ExecutionContext variant and exporting both variants so they don't need to be part of the template code anymore at all?

Yeah i am interested in moving more of the generated code to reusable functions, where would be a good place/package to place those in?

@UnAfraid Thank you for volunteering! The easiest place to put these particular reusable functions is in "github.com/99designs/gqlgen/graphql" as all of the code that gets generated using those functions already at least imports:

	"github.com/99designs/gqlgen/graphql"
	"github.com/99designs/gqlgen/graphql/introspection"
	gqlparser "github.com/vektah/gqlparser/v2"
	"github.com/vektah/gqlparser/v2/ast"

Unless there's an import cycle, or something seems like it needs to belong elsewhere, I haven't been getting any complaints concerned with there being too much in that package, and reorganizing it is easier than moving things out of templates.