Querying a field/argument which doesn't exist fails the whole query rather than just that branch

[dantb]

For example misspelling one of the top-level fields produces something like below, without any data, despite other fields being requested independently.

{
  "errors": [
    {
      "message": "Unknown field 'myFieldd' in select"
    }
  ]
}

Unsure whether this is expected GraphQL behaviour or we should be more permissive. Perhaps it could be configurable? If it is possible I'm happy to be pointed to the relevant part of the code to give it a go 😄

[milessabin]

Sorry, I completely missed this. Yes, the spec allows a partial result in this case. I suspect that this is a special case due to the misspelling being in a top level field ... I'm fairly sure that a similar error in a subobject field would be handled the way you're expecting.