-
Notifications
You must be signed in to change notification settings - Fork 96
Support for input type having a list of complex input type ? #78
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
Comments
I have found that there is similar problem when using |
I think the problem might come from |
Thank you for that, I stumbled upon the same issue and that was helpful. |
If someone wants to cook up a PR for this I can merge it, but I don't have time to look into it myself ⏳ |
@apottere I'm busy but I will try to find the time to fix this issue. |
Hang on, I noticed that while it fixes the GraphQLNonNull situation, it can be extended to do the same for the issue @joel-costigliola raised. I'm adding that to the PR |
I haven't released this library yet, but I can probably set it up today. Might take a day or two to get it synced. |
…hQLModifiedType would fail to resolve the input fields
Meanwhile I think this change in the PR fixes the issue raised by @joel-costigliola |
This issue is also more globally fixed in #94 |
Hi,
I would like to know if the annotations supports introspecting a
List
of complex input type.Here's (simplified) example of what I'm trying to achieve which leads to a
Introspection must provide input type for arguments
error in chrome GraphiQL client .I wonder if I'm doing something wrong or if there is no support of list of complex input types through annotations.
The
SpaceInstanceInput
below is what I'm passing as a parameter of this mutationwhere
SpaceInstanceInput
data structure looks like:The text was updated successfully, but these errors were encountered: