feat: provide better error when field references a type that does not exist #3035
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.
What does this implement/fix? Explain your changes.
This introduces a more helpful error when a field in the Schema references a GraphQL Type that has not been registered to the Schema.
Does this close any currently open issues?
closes #3034
Any other comments?
When registering a field that references a Type that doesn't exist:
Then querying for the field like so:
{ users { nodes { id fakeField } } }Before
A vague error was returned with limited information to quickly identify the issue.
After
A clearer Error is returned