Benjie
> I see this as an editorial change; assuming there's no concerns raised in the next couple weeks I think we should merge it. I'm going to go ahead and...
Agree it should be in section 3; but not sure whether it should be throughout or centralized. We define directive _definition_ validation here: https://spec.graphql.org/draft/#sec-Type-System.Directives.Validation For each of the possible schema...
We should note that there are two use cases for schema directives: 1. to change how a schema entity is formed or behaves (e.g. `foo: [Foo] @connection` to convert to...
@martinbonnin and/or @glasser would you care to elaborate your concerns and/or submit non-normative notes to the GraphQL-over-HTTP spec regarding this. I'm happy to do editorial on them if you only...
Moving this to the GraphQL-over-HTTP WG
@glasser Any interest in raising a PR for this?
Awesome write-up; this all sounds great to me, except the SHOULD > MUST - I feel it's okay to say `SHOULD` with a non-normative note stating that not implementing the...
> Are there examples of popular GraphQL servers that accept POSTs with JSON bodies with no content-type header? The GitHub API: ```sh curl \ -H 'Authorization: Bearer '$GITHUB_TOKEN \ -X...
Without one it seems to have a rate limit of zero currently.
Well said, @yaacovCR; the only point I'd challenge is that formatted types should only reference other formatted types and simple scalars: the fact that `PendingResult` is the same both formatted...