Rest Framework SerializerMutation Error - NoneType is not callable

Hi, I’m using the SerializerMutation class to attempt to create mutations based off of my existing Rest Framework serializers. By taking advantage of the ModelSerializer in DRF, I hoped to avoid having to create all the mutations from scratch with validation and whatnot.

However, the use of the SerializerMutation class isn’t sufficiently explained in the docs. I did this

class ItemMutation(SerializerMutation):
    class Meta:
        serializer_class = ItemSerializer

class Mutation(AbstractType):
    #...other mutations...
    createItem = ItemMutation.Field()

from a simple DRF ModelSerializer

class ItemSerializer(serializers.ModelSerializer):
    class Meta:
        model = Item
        fields = (
            'id',
            'name',
            'description',
            'website',
        )

But Graphiql shows me the following error whenever I try to use the mutation

mutation newItem($data: ItemMutationInput!) {
  createItem(input: $data) {
    name,
    description
  }
}

{
  "data": {
    "name": "Blah",
    "description": "Blah blah blah",
    "website": "https://blah.blah.blah"
  }
}

{
  "errors": [
    {
      "message": "'NoneType' object is not callable",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ]
    }
  ],
  "data": {
    "createItem": null
  }
}

Also, Rest Framework’s serializers can often have multiple actions (mutations) like create, delete, update, etc and the use of SerializerMutation appears to just produce a single mutation - presumably the “create” action. How do I handle the other actions?

[q3aiml]

@abdulhaq-e there was no release of 1.x with SerializerMutation. It was added in July and the most recent 1.x release was 1.3 in April.

For anyone who is interested I opened #261 to try to get SerializerMutation working again for 2.x

[abdulhaq-e]

There must’ve been something wrong with publishing. I didn’t experience it because I had a similar scenario as yours where I had a local copy of graphene-django in my app rather than the version on PyPy.