Files
RosterChief/mobile/mixins.py
Bernard Siebens 4b2b84793f Fix the bottom tab bar never actually highlighting the active screen
active_tab/screen_title were set as class attributes on every screen view,
but only ever threaded into the template context by _PlaceholderScreen's
own get_context_data -- which no real M1-M7 screen has inherited from
since each one got its own concrete implementation. Every screen's own
get_context_data override skipped them, so `active_tab` was always
undefined in the template and the tab bar never lit up. Defaulted both
from the class attributes in PersonScopeMixin (every screen's shared
base) via kwargs.setdefault, so a screen with its own dynamic
screen_title (EventDetailView's event.title) still wins.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ECGMEwrc2k4D8VQuwjstj9
2026-08-21 15:00:16 +02:00

97 lines
5.0 KiB
Python

"""Shared scaffolding for every Member-mode screen (design_handoff_rosterchief_platform/
README.md: "there is no parent app... every per-member screen carries a person
switcher at the top" + "the [Coach/Member] switcher only renders for an account
holding >=1 staff role"). One mixin so M1-M7's views (and the subagents building
them) don't each re-derive this.
"""
from django.conf import settings
from club.services.access import current_season, has_management_access
from members.models import FamilyMembership, Member
from members.views import ClubScopedPublicMixin
from notifications.models import Notification
class PersonScopeMixin(ClubScopedPublicMixin):
"""Resolves the signed-in account's own Member record plus every child
they're a parent/guardian of *in this club* (mirrors members.views.MyFamilyView's
own query -- kept separate rather than imported from there, since that view
is public/unauthenticated-reachable and this one is always behind login).
``?as=<member-id>`` re-scopes the current screen to one managed person,
same as the design doc's horizontally-scrolling chip row -- it re-scopes in
place rather than navigating. ``?as=all`` (or, once there's more than one
managed person, no ``?as=`` at all) scopes to *every* managed person --
that's the default the moment there's actually something to aggregate; a
member on their own, or a parent of exactly one child, has nothing to
aggregate and just lands on that one record, same as before this existed.
Screens that only ever operate on one person at a time keep using
``scope_person`` (``None`` in "everyone" mode); screens that can
meaningfully show several people at once (Home's cards, Calendar's own
"my schedule" listing) should use ``people_in_scope`` instead, which is
always the right list to filter by regardless of which mode is active.
"""
def dispatch(self, request, *args, **kwargs):
self.me = Member.objects.filter(user=request.user).first() if request.user.is_authenticated else None
self.managed_people = self._managed_people(request)
self.scope_everyone, self.scope_person = self._resolve_scope(request)
self.people_in_scope = self.managed_people if self.scope_everyone else ([self.scope_person] if self.scope_person else [])
return super().dispatch(request, *args, **kwargs)
def _managed_people(self, request):
if self.me is None:
return []
children = list(
Member.objects.filter(
family_memberships__role=FamilyMembership.FamilyRole.CHILD,
family_memberships__family__memberships__member=self.me,
family_memberships__family__memberships__role__in=[FamilyMembership.FamilyRole.PARENT, FamilyMembership.FamilyRole.GUARDIAN],
member_of__club=request.club,
).distinct()
)
return [self.me, *children]
def _resolve_scope(self, request) -> tuple[bool, Member | None]:
"""Returns ``(scope_everyone, scope_person)`` -- exactly one of the
two is ever meaningful at a time (the other is ``False``/``None``)."""
requested_id = request.GET.get("as")
if requested_id and requested_id != "all":
for person in self.managed_people:
if str(person.pk) == requested_id:
return False, person
if requested_id == "all":
return True, None
if len(self.managed_people) > 1:
return True, None
return False, (self.managed_people[0] if self.managed_people else None)
def get_context_data(self, **kwargs):
unread_notification_count = 0
if self.managed_people:
unread_notification_count = Notification.objects.filter(club=self.request.club, member__in=self.managed_people, read_at__isnull=True).count()
# Every screen sets these as class attributes (see e.g. HomeView.active_tab),
# but only a subclass that explicitly forwards them into its own
# get_context_data actually gets them into the template -- easy to forget
# (most screens' own get_context_data never touch either one), so default
# them here instead. setdefault, not an outright override: a screen with a
# dynamic title (EventDetailView's event.title) already passes its own
# screen_title through kwargs, and that must win.
kwargs.setdefault("active_tab", getattr(self, "active_tab", ""))
kwargs.setdefault("screen_title", getattr(self, "screen_title", ""))
return super().get_context_data(
me=self.me,
managed_people=self.managed_people,
scope_person=self.scope_person,
scope_everyone=self.scope_everyone,
has_staff_access=self.me is not None and has_management_access(self.request.user, self.request.club),
unread_notification_count=unread_notification_count,
season=current_season(self.request.club),
vapid_public_key=settings.VAPID_PUBLIC_KEY,
**kwargs,
)