Benjie

That seems more complex to me; I think what we have right now is quite a clean separation between runtime values and actual GraphQL specified data: > The errors entry...

You mean things like errors having a `.originalError` property, or something else?

If the payloads add a "requestIndex" property it could fit quite well with #307 and fix these incompatibility issues with newer features; then we could state that where legacy servers...

I've merged the latest `main` into this branch and got it passing tests/etc again; am adding it to the next GraphQL WG.

@magicmark let's merge https://github.com/magicmark/graphql-js/pull/1 into https://github.com/graphql/graphql-js/pull/4422 (you have to do that since you own that repository), then incorporate changes to support https://github.com/magicmark/graphql-spec/pull/1, then I can merge the whole lot into...

@yaacovCR thanks for finding out why Lee explicitly forbade meta fields, even he couldn't remember why he did it! So (pseudocode): ```ts // Get the Type.field GraphQLField instance: const Type_field...

I agree with the drive for this. However, bikeshedding, we need to ensure that it wouldn't conflict with features we might add in future, such as [namespaces](#163). Of course we...

Removing the RFC status from this because it's confusing/out of date - this is actually RFC2 in #794

Is `user: ID` not present instead? That’s the intention. The idea is that you should never deal with the underlying column values for primary keys and instead always use the...

You've not provided an example so it's hard to guide you, but typically you'd do something like: ```sql create table topics ( id serial primary key, title text not null...