fix: __typename
should succeed on root fields
#573
Merged
+15
−7
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.
Description
We already support returning
__typename
fields on user-defined types, such as:... which would give
"Person"
for the__typename
field.However, asking for
__typename
on the rootQuery
orMutation
currently fails, and it should succeed. This is important because some GraphQL clients add__typename
to every field in a query, including the root fields.In other words, these should succeed:
Checklist
CHANGELOG.md
file describing and linking to this PR