A limitation of Mutation?

Hello,

When I do a mutation, I want to be able to return the type directly instead of wrapping it into another field:

So, I want to do:

mutation {
  createPerson {
    __typename // <-- this should give you 'PersonType', ideally
    id
    firstName
    lastName
  }
}

but it seems like in Graphene Django, you have to wrap it inside another field:

mutation {
  createPerson {
    __typename // <-- in reality, this does not give you 'PersonType'
    person {
      __typename // <-- this gives you 'PersonType'
      id
      firstName
      lastName
    }
  }
}

How can I achieve the former?

This is a common pattern. Even the official documentation has this pattern: http://graphql.org/learn/queries/#mutations

[syrusakbary]

Hi @glusa8,

you can use the Output attr in the mutation:

class CreatePerson(graphene.Mutation):
    Output = Person
    ...

[a3ammar]

@honi I made it work by just returning the newly created instance:

def mutate(self, info, **kwargs):
    user = authenticate(info.context, **kwargs)
    if user and user != info.context.user:
        login(info.context, user)
    return user