You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't currently see a good way to do this, the querysets are merged during DjangoConnectionField.resolve_connection which grabs the default_queryset from the model's manager. I've had to extend my own DjangoFilterConnectionField to perform authorization checks. #79 purposes that the object nodes support a get_queryset method which would make this allot easier.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Activity
zbyte64 commentedon Oct 3, 2018
I don't currently see a good way to do this, the querysets are merged during
DjangoConnectionField.resolve_connectionwhich grabs the default_queryset from the model's manager. I've had to extend my ownDjangoFilterConnectionFieldto perform authorization checks. #79 purposes that the object nodes support aget_querysetmethod which would make this allot easier.cocochepeau commentedon Oct 4, 2018
Thanks for your answer. I'm still learning Python/Django so thanks again for the explanation. :)
The idea would be to let us decide directly on the
get_querysetmethod, like in https://docs.djangoproject.com/en/2.1/topics/db/managers/#modifying-a-manager-s-initial-queryset?I'll try to follow #79 as well.
stale commentedon Jun 11, 2019
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
zbyte64 commentedon Apr 14, 2021
You would now define a
ProjetNode.get_querysetto filter by user globally.