-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
Cannot use list-like (Set, Vector, Seq) wrappers as input types #478
Labels
Comments
theobat
changed the title
Cannot use list-like wrappers as input types
Cannot use list-like (Set, Vector, Seq) wrappers as input types
Jul 1, 2020
I just saw #341, maybe I can take care of that too along the way |
the general problem is that graphql does not support custom wrapper types. that why we generate namespaced types for it. type NonEmpty_Int {
elems : [Int]
}
input NonEmpty_User {
elems : [User]
} but this schema will fail. type NonEmpty_Int {
elems : [Int]
}
input NonEmpty_Int {
elems : [Int]
} that why morpheus graphql should generate type like this: # for output types
type NonEmpty_output_Int {
elems : [Int]
}
# for input types
input NonEmpty_Input_Int {
elems : [Int]
} In this case the names do not collide. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey,
I face an issue when I try to use Set Text for example as an input type argument in a query (or a mutation):
I think it's just a matter of adding the right instance in here
I was thinking something like:
As a side note, do you think it would be possible to add a custom wrapper type for the end user (without modifying morpheus) ? Or perhaps a "refiner" so that we can specify length restricted lists for instance ?
Thanks
The text was updated successfully, but these errors were encountered: