Prefetch related with named arguments and objects

Hi @tfoxy, following #22, we are unable to actually know what when we are getting called from: prefetch_related(info, *args[, **kwargs?]) https://github.com/tfoxy/graphene-django-optimizer/blob/1d7032d79bf891aa7842a6ee3d72f860fbf158bd/graphene_django_optimizer/query.py#L241-L250

We could whether have as first or second argument first, last, filter, foo, etc.

We would like to get a **kwargs instead. But we can’t both pass *args and **kwargs to prevent any breaking change for any of the optimizer users.

I believe users using the arguments from *args should be still safe if they are properly using the field name… Otherwise, it will break for sure.

What do you think? Could we get such change in and release it as a major change?

[tfoxy]

Github is not allowing me to transfer the repo as I “don’t have the permission to create repositories on mirumee”. I added you as collaborators for now. We can keep talking through email to coordinate the transfer if you prefer.

[wodCZ]

Hi, have you managed to get this working?