Steve Coffman

See related thoughts https://github.com/shurcooL/githubv4/issues/17

PRs to vektah/gqlparser#166 are very welcome in that repository btw! See some initial work here: https://github.com/vektah/gqlparser/pull/169

I think this was implemented in the gqlgen test client in https://github.com/99designs/gqlgen/pull/1661 and shouldn't be too difficult to accomplish here.

[ugorji/go-codec](https://github.com/ugorji/go) is worth adding to the list above. It is [described here](http://ugorji.net/blog/go-codecgen). Supported Serialization formats are: - msgpack: https://github.com/msgpack/msgpack - binc: http://github.com/ugorji/binc - cbor: http://cbor.io http://tools.ietf.org/html/rfc7049 - json: http://json.org http://tools.ietf.org/html/rfc7159...

@benjaminjkraft What are your thoughts?

The test failures are just that the expectations and the results are a little of sync: ``` // Code generated by github.com/Khan/genqlient version , DO NOT EDIT. ``` vs: ```...

It's a fairly common thing among non-trivial code generators. For instance, https://github.com/deepmap/oapi-codegen/ puts: ``` // Package api provides primitives to interact with the openapi HTTP API. // // Code generated...

So *outside* of genqlient itself (like in an application that uses genqlient as a library and as a tool) I think you could do this: ``` //go:generate go run github.com/Khan/genqlient...

Ah ha! The thing with [pseudo-versions](https://golang.org/ref/mod#pseudo-versions) is that it's just an encoding for a particular revision in a VCS (not just Git). > Pseudo-versions may refer to revisions for which...

See https://github.com/Khan/genqlient/pull/129 where I continued our adventures by updating the expectations and Makefile according to my comments above.