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

What happened?

Stepping through the code and it seems that the same OperationContext is added twice to the active context.Context. This happens just before the call to exec.DispatchOperation at:
https://github.com/99designs/gqlgen/blob/master/graphql/handler/transport/http_post.go#L51

then at the top of exec.DispathcOperation at:
https://github.com/99designs/gqlgen/blob/master/graphql

Look to apply-pr-label-locally.sh for inspiration on how to interact with the GitHub API easily.

• API docs
• gh api repos/guardrail-dev/guardrail/issues/1300/labels -X POST --input <( echo '["chore"]' ) <- POC for addi

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

(Split from #149.)

If you have in your schema

input T {
  f: T  # or `f: T!`
}

then genqlient by default generates

struct T {
  F T
}

which does not compile. Of course you can manually add pointer: true, but we could just do that automatically because it's the only valid way to represent this. Apparently this comes up a lot with Hasura-generated schemas,

Reason/Context

The problem is described here asyncapi/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 😄