[Bug] upmost __typename in mutation finds no resolver

Issues GraphQL
, ,
9

@JatinDevDG @noobloser I faced the same issue as well. Had filed an issue in GraphQL Mesh here: Mesh SDK execution fails · Issue #1339 · ardatan/graphql-mesh · GitHub where we narrowed it all down to this issue.

My mutation from Mesh looked like this:

mutation ($graphqlTools0_updatedAuthMethod: UpdateAuthMethodInput!) {
  graphqlTools0___typename: __typename
  graphqlTools0___typename: __typename
  graphqlTools0___typename: __typename
  graphqlTools0___gqtld0__: __typename
  graphqlTools0___typename: __typename
  graphqlTools0___gqtld1__: updateAuthMethod(
    input: $graphqlTools0_updatedAuthMethod
  ) {
    __typename
    __typename
    __typename
    authMethod {
      __typename
      __typename
      __typename
      id
      __typename
      __typename
      __typename
      authKey
      __typename
      __typename
      __typename
      verificationStatus
      __typename
      __typename
      __typename
      authProviderMethod {
        __typename
        __typename
        __typename
        id
      }
      __typename
      __typename
      __typename
      metadata
      __typename
      __typename
      __typename
      account {
        __typename
        __typename
        __typename
        id
      }
      __typename
      __typename
      __typename
      creationTime
    }
  }
}

and returned the same error:

1
11564×913 78 KB