feat(user_status): set busy status for single calendar events without attendees#61154
Draft
miaulalala wants to merge 1 commit into
Draft
feat(user_status): set busy status for single calendar events without attendees#61154miaulalala wants to merge 1 commit into
miaulalala wants to merge 1 commit into
Conversation
… attendees
Events without attendees (solo/personal blocks) now set
IUserStatus::MESSAGE_CALENDAR_BUSY_SINGLE ("Busy") instead of
MESSAGE_CALENDAR_BUSY ("In a meeting"). Events with attendees continue
to set the meeting status. When both are present simultaneously, the
meeting status takes priority.
Assisted-by: ClaudeCode:claude-sonnet-4-6
Signed-off-by: Anna Larch <anna@nextcloud.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Calendar events without attendees (personal/solo blocks) now set a distinct
MESSAGE_CALENDAR_BUSY_SINGLE("Busy" with 🔴) status, rather than the "In a meeting" status used for events with attendees. When both types of events overlap, the meeting status takes priority.Changes:
IUserStatus::MESSAGE_CALENDAR_BUSY_SINGLE = 'calendar-busy'public API constant (@since 35.0.0)PredefinedStatusServicewith translated label "Busy" and 🔴 iconMESSAGE_CALENDAR_BUSY_SINGLEto the automated-status priority chain inuser_status/StatusService(CALL/AVAILABILITY/OOO all still trump it;MESSAGE_CALENDAR_BUSYalso trumps it)dav/CalDAV/Status/StatusServiceby ATTENDEE presence; revert both message IDs when no events applyTODO
Checklist
AI (if applicable)