-
-
Notifications
You must be signed in to change notification settings - Fork 748
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
Stitching: "01
is not a valid GraphQL type name" when passing json as input to mutation
#3859
Comments
Interestingly that if changing the variables slightly the error disappears. This one works correctly:
Variables:
|
Reproducing repo: https://github.com/gao-artur/graphql-stitching-3859 |
The issue is that objects are serialized to object value nodes that follow |
@michaelstaib can you propose some workaround? This is a blocking issue for us for replacing graphql-dotnet with HC. Unfortunately we can't use the workaround from my second comment because Apollo that sits in front of HC gateway will normalize variables to the first form. |
I do not have a workaround for this. The release of the stitching release is at the end of August so it is not that far off. The issue here is the nature of the scalar. The August release focuses solely on stitching and will fix such errors. We however would accept a PR for a patch release of 11.3.x. So, if you can debug it and find the exact cause we can get it in a release for you. The core team is really busy at the moment working on the new stitching gateway release which fixed such issues thus we really have no capacity for a quick fix. All people of the core team do this in their free time and are not paid for this work. I get that this might block you but a solution will be in the August release. |
@michaelstaib challenge accepted 😀
I'm wondering what will be the correct fix: changing |
@PascalSenn can you have a look since you added this? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Please reopen, there is unfinished PR to fix the issue. |
Hey,
The following issue reproduced only on stitching service, everything works correctly on regular service.
The schema:
PropertiesDictionary
taken from hereRequest:
Variables:
Response:
The text was updated successfully, but these errors were encountered: