Benjie

Also: ``` [postgraphile]: PASS postgraphile __tests__/queries/v4/streamLoads.test.graphql (7.963 s) [postgraphile]: ● Console [postgraphile]: [postgraphile]: console.error [postgraphile]: GraphileInternalError: Received an error when stream was already finished: Error: Test transaction has already been...

Recreation using the reference implementation below; note that the schema and operation are both valid but that the resolver itself is never executed due to the behavior of [CoerceArgumentValues()](https://spec.graphql.org/draft/#CoerceArgumentValues()) -...

This isn't quite an RFC yet, but it should be.

Here are the options I see: 1. Forbid interface fields from having default values on their arguments. 2. If an interface field argument has a default value, each implementation must...

Consider this schema: ```graphql interface I { field(int: Int! = 1): Int } type T implements I { field(int: Int! = 1): Int } type Query { i: I }...

I think option three with the strong recommendation that they pretend it’s option 2 is fine; that way tooling can more easily enforce it. It’s also the least breaking for...

Just to be clear: option 2 could change the meaning of existing queries, option 3 would not. I think option 3 with a "SHOULD" for having the values match is...

Honestly it depends how much we want to encourage it; but right now I'm thinking we forbid it with a schema lint rule in GraphQL.js and then let you pass...

Duplicate of https://github.com/graphql/graphql-spec/issues/568 - please re-post any new interesting feedback to that thread. Also related: https://github.com/graphql/graphql-spec/issues/236

We already allow `extend type Query` to exist. Can you not simply omit the `{}` when there's nothing in the braces? I'm pretty sure this parses, though I haven't checked:...