Ben Kraft
Ben Kraft
Right now the spec says that, for example, if the schema does not define a mutation root type, then the schema does not support mutations. But there's no validation rule...
In particular, obviously it's a breaking change if we change the signature of an exported symbol, like `graphql.Client` or `generate.Main`. But are these breaking changes? The first question is: do...
For both the `bindings` option, and the soon-to-be-added `typename` option, we validate that two selection sets are equal. Right now we demand that they even have the fields in the...
There are a few potential ideas here, which may coordinate or conflict. First, any code that's using genqlient should be a great match for one of the libraries that does...
If you do ```graphql # @genqlient(...) query Q(arg: T!) { field { subfield } } ``` then the directive applies -- and must be legal for -- not only `query...
It's been a few months; not that much is new but when we get a chance we should release a new version. Probably can be 0.5.1 since there's not that...
If you do `UPDATE_SNAPSHOTS=1 go test ./...` that will: 1. run the snapshot tests, updating any changed snapshots 2. run the integration tests and (if you have tokens) example tests...
If you want to apply some option to all cases where a particular field of a particular type is referenced in an operation (most commonly an input type) we have...
(Split from #149.) If you have in your schema ```graphql input T { f: T # or `f: T!` } ``` then genqlient by default generates ```go struct T {...
Consider the following queries: ```graphql # @genqlient(omitempty: true) query Q1(input1: MyInput) { ... } query Q2(input2: MyInput) { ... } ``` In this case, we generate a type `MyInput` which...