C Chan

@jieter I think you might have a better idea than me.

I like the idea if you can get rid of the "Node and Edge" from the query that would make it cleaner and get rid of the `interface = (Node,)`...

Not ready for production. I would go for Graphene if you want graphql for production. There are still issues that are not addressed like nested create mutations, django choices /...

For graphene I think it was a meta class used to do the `all_fields` So they have: ``` class Object: class Meta: model =Django model fields = (fields, fields)a list...

@bellini666 Ok it works so it is a docs issue I am going to update it. Here is the [PR](https://github.com/strawberry-graphql/strawberry-graphql-django/pull/149)

@bellini666 Ok so I changed `partial=True` and entered my query ``` mutation newPerson ($name: String!, $address:ID!){ createPerson(data: {name: $name, address: {id: $address}}) { id name address { id name }...

@bellini666 That does not work either If I try: ``` mutation newPerson ($name: String!, $address:ID!){ createPerson(data: {name: $name, address: $address}) { id name address { id name } } }...

@bellini666 I am just doing a mutation where I set the foreign key by using an id. I did the exactly mutation query you have on your second mutation input...

I think it is good to switch to GraphiQL although I will miss the color scheme on Playground. GraphiQL does autofill some of the queries making it easier to use.

I am having the same issue it is not loading some library in primevue which prevents the dropdown from working.