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
[...]
``

Reason/Context

The problem is described here asyncapi-archived-repos/playground#79. It must be clear that returned data is not content but an object with content and metadata + what is this metadata, and that it is only with React renderer.

Description

Probably JSDoc must be only updated. Of course, some additional section in the readme would be also welcomed 😄

With a file

---
description: 400 - The request was malformed or missing a required field.
content:
  application/json:
    schema: { $ref: '#definitions/BadRequestResponse' }

definitions:
  BadRequestResponse:
    description: Optional information about how the request was bad.
    type: object
    properties:
      fieldName:
        description: >-
          If this error

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