Graphene query single and multiple model filtering

[Eraldo]

As a developer, I want to be able to define limitations on which model instances can be fetched by a DjangoFilterConnectionField even if queried indirectly as a reverse foreign key relation of another model.

Currently my filters only apply where I explicitly set them via DjangoFilterConnectionField -- not on related entry points.

I saw some code from stephrdev which would fix this. With the comment that it would probably not work as is in my repo.

stephrdev: Can you please point me to code again?

[rdev]

Hi! As I said in your #2, I have no idea what this project is and why I was tagged on it

[Eraldo]

Sorry, I meant another person and mixed up the usernames. ;)
(I menat @stephrdev)

[rdev]

No worries 👍

[stephrdev]

To control the available model instances on a manager (no matter which direction) you can override the resolve_<[related] manager name> or replace the connection class of the object type.

To prevent related managers all around in the graph schema, it is always a good idea to use only_fields Meta option on DjangoObjectType to control which fields are exposed at all. You might not need all of the fields.