fix(compiler): fix error message for missing subselection #865
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Given:
```graphql
type A { b: B }
type B { field: Int! }
```
and a selection against `A`:
```graphql
{ b }
```
The error message said `B.b` must have a subselection. But `B.b` does
not exist. We confused the return type of the field `b` and its parent
type.
Now you correctly get an error saying that `A.b` must have a
subselection.
lrlna
approved these changes
Jun 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Given:
and a selection against
A:{ b }The error message said
B.bmust have a subselection. ButB.bdoes not exist. We confused the return type of the fieldband its parent type.Now you correctly get an error saying that
A.bmust have a subselection.