mroderick / codebar-planner / 22257859468

96%

master: 95%

push

github

feat: cache member attending event IDs to eliminate N+1 queries

Motivation:
The events and meetings index pages were making N+1 queries when checking
if a logged-in member was attending each event. Each call to
@user.attending?(event) triggered a database query.

Analysis:
- Before: 40 queries for 40 events
- After: 3 queries (one each for invitations, workshop_invitations, meeting_invitations)
- The cache returns a Set of all event IDs where the member has an accepted
  invitation, making subsequent lookups O(1) Ruby operations.

The cache is invalidated when an invitation's attending status changes via
after_save callbacks on Invitation, WorkshopInvitation, and MeetingInvitation models.
This ensures the cache stays fresh on the next request after RSVP.

21 of 21 new or added lines in 5 files covered. (100.0%)

3294 of 3445 relevant lines covered (95.62%)

44.85 hits per line