Yaacov Rydzinski

Were you able to figure this out? I think we need a version of HoistField that copies prior to hoisting, or maybe a generic transform that copies, and then you...

This sounds like a great challenge, but it’s been some time. Are you able to set up a very minimal breaking example as either PR with test or GitHub repo...

That looks right, start from root types rather than type map

I guess the question is why (or why not) some errors should be considered Request errors, for example, submitting a mutation operation when no mutation root type exists. it is...

But if you don’t validate, you can get user errors during field execution so ???

@IvanGoncharov that definition while clean is a bit circular, whether or not a path should be empty depends on whether we have started execution…

if it it made optional, might be a good idea to also roll in the change of the “query” term to “document” or “source” i prefer source as is more...

> Should we change [RFC: OneOf Input Objects #825](https://github.com/graphql/graphql-spec/pull/825) to only require one non-null field rather than just one field? Could you expand on this sentence? Thanks so much!

Actually, if I understand the concern, it is a question of whether you can provide something like: ```json { "dog": null, "cat": { "meows": true, } } ``` to an...

see: https://github.com/graphql/graphql-spec/issues/518