Multiple query/mutation fields short circuited by __typename in apollo, apollo 4, and envelope plugins

[SimplyKnownAsG]

A mutation (probably query too) with multiple fields (operations calls) will short circuit checking the @constraint in the subsequent inputs when using the apollo, apollo 4, and evenelope plugins.

Example (using the existing test typeDefs)

mutation multipleMutations($input1: BookInput, $input2: BookInput) {
  one: createBook(input: $input1) {
    title __typename
  }

  two: createBook(input: $input2) {
    title __typename
  }
}

Non-conforming $input2 values are ignored. I think it might have something to do with this BREAK, but I haven't figured that out yet.

[WenInCode]

I'm running into the same issue on a query that has two top level fields. It seems that it shouldn't completely break out of the visitor if it runs into a __typename despite it not existing in the typedef.

[aaugmentum]

Hi @confuser, We have the same issue, traversal stops when it sees __typename field, and every field with input object which comes after __typename field is not validated. Are you planning to fix it?