feature: Support inline fragments without a type condition #123
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
A graphql query with an inline fragment that doesn't have a type condition would be considered an invalid query.
See the Inline Fragments section of the graphql spec which shows that the type condition is optional and includes examples of queries with inline fragments without a type condition.
Solution
There were several places where it was assumed that a fragment always had a type, so I had to update the parser, transformer, static validator and the selection resolution. Basically if the type condition isn't specified, then we can skip the type check and continue using the parent type.