Ben Boeckel

Hmm. At least Github tends to give back line/column information based on the query sent. Right now, that corresponds with the actual query file, but trimming down would mean that...

As I said elsewhere, this can result in line/column information in error messages from servers not matching the source anymore. If this is done, it should be an option.

https://docs.travis-ci.com/user/cron-jobs/

It seems that `type Int = i64` has been there since the beginning (2024a4f486361cdb3c4399794e614dbd81e77746), so nothing in the commit history at least. I also suspect that `type ID = String;`...

@tomhoule Candidate for 1.0?

Sure, but it will need a release note to indicate the breaking change. Or changes if you also tackle the ID mismatch.

Thanks. I've filed an issue: graphql-rust/graphql-parser#53

I'll try and take a look at it this weekend, but I can't guarantee anything.

IIRC, it is hit if you say `query { someUnknownField }`. It was a typo on my part, but the error message didn't help :) .

I think this would massively complicate things. What would `IsValidVariablesFor` be? Do we lose type safety because of this? Same with the response trait. Other than `Cow` (maybe optionally using...