-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Add support for maps rather than using a scalar as a workaround #4
Comments
Hi, Sorry at the moment maps are not supported due to limitations of the graphQL. I added this stupid implementation as a quick solution to the problem... I would try to avoid using maps with graphql if possible. 99designs/gqlgen#663 If this issue of gqlgen will be fixed I will be able to implement a map as a list of map entries and generate resolvers that translate the list into a go map. |
thanks for info, i'm subscribe to gqlgen to check this issue |
If I manage to merge this PR, the issue will be pretty much fixed 99designs/gqlgen#1404 |
Added map support as an array of entry types. However if you wish to generate go-lang bindings as well, instead of using the official |
how to avoid this piece of code?
The text was updated successfully, but these errors were encountered: