Conversation
This commit introduces a new collapsible header category "System Alerts" in the `RoomsList` widget. Rooms tagged with `TagName::ServerNotice` are now filtered into this category, which is displayed at the top of the list. The header is collapsed by default and styled with a gray background to de-emphasize its importance, as requested. - Added `HeaderCategory::SystemAlerts`. - Updated `RoomsList` to track and display system alert rooms. - Prioritized system alert categorization over direct/regular room status. - Updated UI drawing logic to render the new category. Co-authored-by: kevinaboos <1139460+kevinaboos@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Implemented the "System Alerts" category in the
RoomsListwidget. This category groups rooms with theTagName::ServerNoticetag, displaying them at the top of the list in a collapsed-by-default section with a gray header. This ensures system notices are separated from regular and direct message rooms.PR created automatically by Jules for task 5979748447562730118 started by @kevinaboos