Chore: drop get_objects_for_user_owner_aware (#14457)

Drops get_objects_for_user_owner_aware. Callers now use restrict_queryset_to_visible.

The same question was answered two ways, and the guardian path did not deny
deactivated users the way permitted_object_ids does.
This commit is contained in:
Trenton H authored and GitHub committed 2026-10-21 15:46:23 +00:00
1 parent 376e865989
commit a3b358bad7
5 files changed
+102 -80

No files matched your search

+3 -3
View File
@@ -2,8 +2,8 @@ from django.utils.translation import gettext as _
from rest_framework import serializers
from rest_framework.exceptions import PermissionDenied
from documents.permissions import get_objects_for_user_owner_aware
from documents.permissions import has_perms_owner_aware
from documents.permissions import restrict_queryset_to_visible
from documents.serialisers import CorrespondentField
from documents.serialisers import DocumentTypeField
from documents.serialisers import OwnedObjectSerializer
@@ -68,10 +68,10 @@ class AccountField(serializers.PrimaryKeyRelatedField[MailAccount]):
if user is None:
return MailAccount.objects.none()
return get_objects_for_user_owner_aware(
return restrict_queryset_to_visible(
MailAccount.objects.all(),
user,
"change_mailaccount",
MailAccount,
).order_by("-id")