🎨 Palette: [UX improvement] Clear status bar state on error#100
🎨 Palette: [UX improvement] Clear status bar state on error#100
Conversation
Fixes an issue where status bar tooltips and background colors persist even when transitioning to an error or unknown state. By explicitly clearing `statusBarItem.backgroundColor` and setting a contextual tooltip, we prevent lingering warning/error colors and misleading UI feedback in VS Code. Co-authored-by: raccioly <63126795+raccioly@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: The UX enhancement clears the
statusBarItem.backgroundColortoundefinedand updatesstatusBarItem.tooltipto provide contextual text when a JSON parse error or calculating exception occurs in the extension.🎯 Why: The VS Code extension API persists the background color of status bar items across updates. If the score threshold drops below a passing limit, it sets a warning background color. If the next refresh hits an unknown error (e.g. unparseable JSON), the extension resets the text but the background color lingers, confusing users into thinking there is a warning state instead of an unknown error.
📸 Before/After: Visual change in the VS Code editor status bar (removes lingering warning/error colors when in error states, updates tooltip context).
♿ Accessibility: Ensures that status changes correctly reset their visual affordances so users depending on visual feedback (or screen reader tooltips) are not provided stale, inaccurate contexts.
PR created automatically by Jules for task 579763078011676449 started by @raccioly