-
Notifications
You must be signed in to change notification settings - Fork 184
KeyError
when parsing result using fragment and nested field
#445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
type: bug
An issue or pull request relating to a bug
Comments
Thanks for the detailed bug report. I'm looking into it. As a workaround, it seems to work if you put the fragment at the end like this:
|
Thank you for the quick reply! Your proposed workaround works for my purposes 👍 |
leszekhanusz
added a commit
to leszekhanusz/gql
that referenced
this issue
Nov 14, 2023
It should be fixed in pre-release v3.5.0b7. |
michael-nml
added a commit
to NannyML/nannyml-cloud-sdk
that referenced
this issue
Nov 15, 2023
Includes a fix for issue we encountered using fragments. See graphql-python/gql#445
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Executing a query that contains a fragment next to a nested field results in a
KeyError
when parsing results.Example query:
Stacktrace:
To Reproduce
Following test case reproduces the issue using the
StarWarsSchema
defined intests/starwars/schema.py
Expected behavior
Parsing without error so that the assertion passes.
System info (please complete the following information):
The text was updated successfully, but these errors were encountered: