ManyToMany relation with wrong type

[amille44420]

I got into an issue with DjangoObjectType to convert a Django model into a GraphQL type ; On many to many relationships I get a list of the model owning the relation instead of the related model.

Here are the models to reproduce the issue

from django.db import models

class Child(models.Model):
    pass

class Parent(models.Model):
    children = models.ManyToManyField(Child)

and the schema definition

import graphene
from graphene_django import DjangoObjectType
from . import models

class Child(DjangoObjectType):
    class Meta:
        model = models.Child

class Parent(DjangoObjectType):
    class Meta:
        model = models.Parent

class Query(graphene.ObjectType):
    parents = graphene.List(Parent)

    def resolve_parents(self, args, context, info):
        return models.Parent.objects.all()

schema = graphene.Schema(query=Query)

And the test file

import graphene
from django.test import TestCase
from graphene_django.fields import DjangoListField
from . import schema

class M2MTestCase(TestCase):
    def setUp(self):
        schema.schema.build_typemap()
        # get the graphql type for the field related to the children
        self.field_type = schema.Parent._meta.fields['children'].get_type()

    def test_graphql_types(self):
        # we must get a django list field
        self.assertEquals(isinstance(self.field_type, DjangoListField), True)
        # behind it we've a graphql list
        self.assertEquals(isinstance(self.field_type.type, graphene.List), True)
        # it must be a list of Child
        self.assertEquals(self.field_type.type.of_type, schema.Child)

[jsenecal]

I actually have the same issue - have you found a workaround?

[jsenecal]

I actually figured that this is a duplicate of #222 but with a different approach to the problem

[amille44420]

So far the only workaround I got is to override the definition myself

class Parent(DjangoObjectType):
    children = graphene.List(Child)

    class Meta:
        model = models.Parent

But I believe we should not have to do that to make it works.

[spockNinja]

What version are you guys using? This should have been resolved by #181. However, it doesn't look like that fix was released until 2.0. So if you're on a 1.X version, you might have to point to a specific commit or something in your pip requirements.

[dopeboy]

@amille44420 were you able to try v2?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ish-vasa]

i'm on v2, django 2.3 and none of my m2m on my models autogenerate if that helps anyone

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.