🎨 Palette: Semantic Error Colors in TUI - #58
Conversation
Improve TUI accessibility by highlighting error statuses in red instead of defaulting to green success indicators. Co-authored-by: omsingh02 <215121080+omsingh02@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. |
💡 What:
Added semantic red color styling to the TUI footer when the status indicates an error (e.g., contains "[!]" or "error").
🎯 Why:
Previously, if a status message did not explicitly match "Listening" or "Processing", it defaulted to a green status indicator, even for failures like
[!] Recognition error: .... This gave confusing visual feedback. Now, errors are rendered in bold red, providing clear semantic cues for the user.📸 Before/After:
Before: Errors showed up with a green circle and cyan border.
After: Errors show up with a red circle, red text, and red border.
♿ Accessibility:
Improves color-coded feedback accessibility, ensuring users immediately recognize destructive or failed actions through correct semantic coloring instead of conflicting success indicators.
PR created automatically by Jules for task 1564429850028212804 started by @omsingh02