Tormod Haugland comments

Results 26 comments of


                                            Tormod Haugland

many_to_many_extras not working for ArrayReferenceField (djongo)

Noted. I'll try to get this fixed and released for 0.8.0.

Many to Many extras with through model

Hi! Thanks for the report and the provided code snippets. I will have a look at this during the course of the week.

Many to Many extras with through model

Hi. I am able to reproduce this. Scheduled for release with 0.8.0.

Many to Many extras with through model

Hi again. After looking into this again I am unable to reproduce this. Please see the latest test from develop: https://github.com/tOgg1/graphene-django-cud/blob/c6e630ec48a1c3204e8e7ef8c939c0f32905c789/graphene_django_cud/tests/test_create_mutation.py#L696

Excluding nested fields in create mutation

Hi @geekashu! You have to exclude inside the extra as such: ```python class CreateStackMutation(MutationMixin, DjangoCreateMutation): """Create dynamic settings""" class Meta: model = Stack exclude_fields = ('modified', 'created',) one_to_one_extras = {"email":...

Allow overwriting return ids in Batch Delete

Great! But please use the get_return_id from DeleteMutation as the template for your implementation, as it contains some additional complexity which can be useful here as well.

Add multiple database support for mutations

I'm assuming you want to be able to control this on a per-mutation level, say? I.e. using automatic routing will be insufficient?

Add multiple database support for mutations

Roger that. Would you also need to be able to control routing on nested relationships?

Add multiple database support for mutations

Another comment here: Will overriding `get_queryset` be sufficient here?

Add auto_context_queryset_filter Meta field

After closer consideration, I am unsure whether or not this should actually be a part of the library. At some point, we'll end up putting our (this library's) hands in...