Validate inline fragments on GraphQL objects

Using an inline fragment with type condition should be validated when used as part of the selection set of a GraphQL object. Sample incorrect query (see this comment)

query GetPullRequests($org: String!) {
  organization(login: $org) {
    name
    url
    repositories(first: 100) {
      nodes {
        name
        pullRequests(first: 100, states: OPEN) {
          nodes {
            number
            title
            url
            body
            author {
              login
            }
            reviews(last: 10, states: APPROVED) {
              nodes {
                author {
                  login
                }
                ... on User {
                    __typename
                    bio
                    id
                  }
              }
            }
          }
        }
      }
    }
  }
}

[Zaid-Ajaj]

I feel like I’m bugging more than debugging lol

No, feedback from real use cases are really valuable and I couldn’t otherwise fix all of these problems without your input 😉 In any case, I just released another fix for the naming collisions as of v1.7.3 and this time I’ve added integration tests for the Github schema that generate and compile a project based on your GraphQL queries so now we know for sure it works without accidentally breaking it 😄

[mattsonlyattack]

I feel like I’m bugging more than debugging lol