graphene-django-cud icon indicating copy to clipboard operation
graphene-django-cud copied to clipboard

Easy and painless CUD-mutations for graphene-django.

Results 35 graphene-django-cud issues
Sort by recently updated
recently updated
newest added

I have nested structure of one-to-one fields. I have the following models: ``` class Account(models.Model): name = models.CharField(max_length=100) class OrgMember(models.Model): account = models.OneToOneField(Account, on_delete=models.CASCADE, related_name="member") class Org(models.Model): owner = models.OneToOneField(OrgMember,...

There is likely a use case for having a DjangoUpsertMutation.

enhancement

Currently, return ids in both the `DeleteMutation` and the `BatchDeleteMutation` are base64 encoded using the `to_global_id` function in `graphql_relay`. The purpose is to ensure that between different models, ids of...

``` python version 3.10.3 django version 4.0.3 graphene-django from main branch latest commit by date of posting(f6ec0689c18929344c79ae363d2e3d5628fa4a2d) graphene_django_cud version 0.10.0 ``` I was trying to create a DjangoCreateMutation(actually it fails...

That change will allow nested attribute fetching on auto_context_fields: ``` class ItemNode(DjangoCreateMutation): class Meta: model = Item auto_context_fields = { 'profile': 'user.profile' } ```

here is my model ``` class Account(models.Model): parent = models.ForeignKey( to="backend.Account", null=True, blank=True, on_delete=models.SET_NULL, related_name="child_accounts" ) ``` here is my mutation ``` class CreateAccountMutation(DjangoCreateMutation): class Meta: model = Account foreign_key_extras...

Hi I have these models ``` class package(models.Model): items = models.ManyToManyField('product.item', verbose_name=_("Items"), related_name="package_items") class item(models.Model): products = models.ManyToManyField('product.product', verbose_name=_("Products"), null=True, blank=True) class product(models.Model): options = models.ManyToManyField("product.option", verbose_name=_("Product options"), null=True, blank=True)...

In the many-to-one and many-to-many extras, there is currently a way to specify `"exact"`, which essentially purges all past entries and creates new ones following the given inputs, such that...

`many_to_one_extras` -> `many_to_many_extras` in the relevant section.