codegen

One of the specific advantages of the wire approach is that it generates code that's relatively readable compared to reflect-based equivalents. When wire.Value is used on a small by-value type, there's no need for the value to live in a global variable - the expression could instead be used literally inside the generated code, which would make the code easier to follow, and more similar to the c

Discussed in 99designs/gqlgen#1854

go: found github.com/99designs/gqlgen/example/federation/accounts/graph/model in github.com/99designs/gqlgen/example v0.0

Stacktrace:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x40 pc=0x6d064d]

goroutine 1 [running]:
github.com/Khan/genqlient/generate.(*generator).preprocessQueryDocument.func1(0xc000174240, 0xc0000dac00)
	/home/benkraft/.go/pkg/mod/github.com/!khan/genqlient@v0.4.0/generate/generate.go:188 +0x2d
[...]
``

Hi there, thanks for this project. Very happy so far.

We're trying to migrate to scala 3, and on of the things which came up was this.

I need to make this manual change to use a generated http4s client, in Implicits.scala

-    implicit val showString = build[String](Predef.identity)
-    implicit val showInt = build[Int](_.toString)
-    implicit val showLong = build[Long](_.

Reason/Context

This is to replace the old AsyncAPI logo in this repo's README with the banner attached below that represents the new branding.

Here are a few guidelines for this change as well:

1. Make sure you are using Markdown syntax

The Generated Client API is remains largely undocumented...

It would also be awesome if we could include the documentation of the API in the Generated DSL