n:m queries are not correctly handled about graphcraft HOT 8 CLOSED

you are right. It indeed is the case. I will see how we can fix it. It seems like an issue coming from graphql-sequelize.

from graphcraft.

on graphql-sequelize-crud it was fixed, but seems that it uses complex loop:

https://github.com/Yehonal/graphql-sequelize-crud/blob/master/src/getSchema.ts

from graphcraft.

Here you can find the issue asked on graphql-sequelize:

mickhansen/graphql-sequelize#386

from graphcraft.

I have an idea how to fix it, there are two options, one to include through model's attributes in both n:m models and whenever someone queries we modify sequelize query output accordingly.

from graphcraft.

But it's a good catch, I didn't run into such situation so far but i guess i will think about and let you know as well.

from graphcraft.

This is how it's handled by graphql-sequelize-crud:
i've 3 tables for n:m association (recipe 1->n recipeIngredients n<-1 ingredients) where recipeIngredients table has quantities attribute inside
and this is the graphql query:

{
  recipes { // query to retrieve recipe from table (recipes)
    name   // recipe name
    Ingredients{ // query to retrieve ingredient relation
      edges {
        quantities // this is the field of relational table (recipeIngredients)
        node {  // the node is the true ingredient table (ingredients)
          name  // name of the ingredient 
        }
      }
    }
  }
}

from graphcraft.

i'm working on it using "sequelizeConnection" from graphql-sequelize

from graphcraft.

fixed on PR

from graphcraft.