Repository navigation
Skip the fullscreen alert for a meeting joined early - #1037
bluejay-creators wants to merge 2 commits into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughMeeting joins now use a shared helper that opens the event and records it as joined only when it has a meeting link. The record store updates fullscreen notification records. Tests cover join recording and subsequent notification handling. ChangesJoined Meeting Notifications
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Sequence Diagram(s)sequenceDiagram
participant AppModel
participant NotificationRecordStore
participant FullscreenNotificationHandling
AppModel->>AppModel: Open event
AppModel->>NotificationRecordStore: Record event when meetingLink is non-nil
NotificationRecordStore->>FullscreenNotificationHandling: Save updated fullscreen records
Suggested reviewers: Merge Risk: ⚪ Minimal · up to
|
What and why
Joining a meeting early through MeetingBar does not stop its fullscreen alert. When the alert time arrives, the fullscreen window still covers the screen, interrupting the meeting you are already in. The "already handled" record for the fullscreen alert was written only when the alert itself fired, never on join.
Joining now writes that same record for the event (
NotificationRecordStore.recordJoined), through a newAppEnvironment.recordMeetingJoinedhook called fromAppModelfor.joinMeetingand.joinNearestMeeting, so it covers the menu, the status-item shortcut and notification Join actions. It is skipped when the event has no meeting link, since opening then falls back to the event page rather than joining.User-visible behavior
A meeting joined through MeetingBar before its alert time no longer shows the fullscreen alert. Meetings you have not joined still get it. If the meeting is changed afterwards (new last-modified date), the alert applies again, as before. Joins made outside MeetingBar are unchanged.
Regression risks
Notifications: only the fullscreen processed-event record is written, using the existing format and cleanup; auto-join and the event-start script are unaffected. Meeting opening:
openMeetingis called exactly as before.Verification
testFullscreenNotificationSkipsEventJoinedEarly: two due events, one joined first. It fails without the fix (["E1", "E2"]alerted) and passes with it (["E2"]only).testJoiningRecordsOnlyEventsWithAMeetingLink.Release-sensitive changes (if any)
None. Suggested release note: "Joining a meeting early no longer brings up its fullscreen alert at start time."
Summary by CodeRabbit