🎨 Palette: Improve status bar state transitions#97
Conversation
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
Updated the VS Code extension to explicitly reset the status bar background color to
undefinedwhen the CDD score check fails or enters an unknown state. Also added descriptive tooltips to explicitly indicate 'Unknown' or 'Error' states, and fixed a syntax error by converting theactivatefunction toasync.🎯 Why
In the VS Code API, custom background colors (like
warningBackground) persist across state updates unless explicitly reset. If an error occurs, a previous warning state's color could linger, providing confusing and inaccurate visual feedback to the developer. The added tooltips ensure developers have context for the status bar icon.📸 Before/After
$(shield) CDD: ?) but remain colored warning yellow/red, with no explanation in the tooltip.♿ Accessibility
Improves accessibility by ensuring visual color cues accurately match the system's underlying state, and by providing explicit text via tooltips for users who may rely on screen readers or hover interactions rather than color alone to deduce status.
PR created automatically by Jules for task 4385439644776734721 started by @raccioly