-
Notifications
You must be signed in to change notification settings - Fork 23
add support for many-to-many relationships in json2graphql #4
Comments
Copying of my last post from json2graphql: I think the best solution would be:
We already have the _id naming convention for single relationships, so using _ids would be the logical solution for multiple. And we could always combine this with the named key naming convention:
I've updated Blowson to correctly handle arrays like in the example above: https://github.com/FrediBach/Blowson |
I've added support for custom key names in Blowson version 0.9 :-) |
any chance there will be support for many-to-many relationships soon, its a pretty common use case these days |
When you implement the many2many feature, would you please also keep in mind to support (even in further future) junction table filters? Say I have tables I guess to support that filter will have some impact on the query argument interface. Thanks in advance |
@wawhal Hi wawhal. This seems interesting and the only issue that seems not be taken. I am a complete newbie and have never used Hasura. Is it a good issue for me. I am willing to learn hasura and can also dive in the codebase. If yes, can you assign it to me? Thanks. |
@rv404674 we don't assign issues for Hacktoberfest. Here are the guidelines you can follow for contributions: https://github.com/hasura/graphql-engine/wiki/Hacktoberfest-2019-%F0%9F%8E%89. If there is a draft PR linked to the issue, it means someone is working on it 🙂 |
Moved from hasura/json2graphql.
Originally opened by: @FrediBach
The text was updated successfully, but these errors were encountered: