Querying a field/argument which doesn't exist fails the whole query rather than just that branch
Open
Nobody has claimed this yet.
bug
- Dominant language
- Scala
- Stars
- 189
- Forks
- 32
- Avg merge
- 18h 31m
- Merged PRs (30d)
- 37
Description
For example misspelling one of the top-level fields produces something like below, without any data, despite other fields being requested independently.
{
"errors": [
{
"message": "Unknown field 'myFieldd' in select"
}
]
}
Unsure whether this is expected GraphQL behaviour or we should be more permissive. Perhaps it could be configurable? If it is possible I'm happy to be pointed to the relevant part of the code to give it a go 😄
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source files, tests, or entry points. Start by locating GraphQL validation and execution handling for unknown fields, then determine whether partial results are expected and what a configurable behavior would require.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, scala
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100