Add support for maps rather than using a scalar as a workaround about go-proto-gql HOT 4 CLOSED

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.

from go-proto-gql.

thanks for info, i'm subscribe to gqlgen to check this issue

from go-proto-gql.

If I manage to merge this PR, the issue will be pretty much fixed 99designs/gqlgen#1404

from go-proto-gql.

Added map support as an array of entry types.
Check for example:
https://github.com/danielvladco/go-proto-gql/blob/master/example/codegen/pb/constructs.graphqls#L281-L284
https://github.com/danielvladco/go-proto-gql/blob/master/example/codegen/pb/constructs.graphqls#L273

However if you wish to generate go-lang bindings as well, instead of using the official github.com/99designs/gqlgen generator you will need to use this fork github.com/danielvladco/gqlgen

from go-proto-gql.