-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Nested @requires generates incorrectly in generated federation file #1704
Comments
CFitzgerald212
changed the title
Nested @requires generates poorly in generated federation file
Nested @requires generates incorrectly in generated federation file
Nov 11, 2021
Not sure if this helps, but you may try marking |
carldunham
pushed a commit
to carldunham/gqlgen
that referenced
this issue
Nov 11, 2021
@CFitzgerald212 sorry about that. Just saw this myself, should have a tested fix soon. |
2 tasks
carldunham
pushed a commit
to carldunham/gqlgen
that referenced
this issue
Nov 13, 2021
carldunham
pushed a commit
to carldunham/gqlgen
that referenced
this issue
Nov 14, 2021
entity resolver tests for nested @requires fields
StevenACoffman
pushed a commit
that referenced
this issue
Nov 18, 2021
This was referenced Jan 15, 2022
Open
1 task
This was referenced Mar 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
I'm using the recently implemented nested @requires directives to try to pass through an id of a subtype to a field extension, and the generated file is not able to correctly unmarshall the nested id field, resulting in a null id being passed through.
Schema
Generated federation output
Expected generated output
What this does
When resolving User.extension, subType.ID = "null"
versions
The text was updated successfully, but these errors were encountered: