Skip to content

🎨 Palette: Improve status bar error context and state resets#88

Draft
raccioly wants to merge 1 commit intomainfrom
palette/fix-vscode-status-bar-errors-13486129242837321735
Draft

🎨 Palette: Improve status bar error context and state resets#88
raccioly wants to merge 1 commit intomainfrom
palette/fix-vscode-status-bar-errors-13486129242837321735

Conversation

@raccioly
Copy link
Copy Markdown
Owner

@raccioly raccioly commented May 6, 2026

💡 What

Updated vscode-extension/extension.js to ensure the status bar explicitly resets its background color when transitioning to an unknown state (backgroundColor = undefined). Also, updated the error catch block to clearly show an error icon, error background, and the exact error message in the tooltip, instead of silently fading to an unknown state.

🎯 Why

When execSpecguard failed or returned non-JSON content, the extension either showed an unhelpful CDD: ? with lingering background colors from previous warnings, or completely hid the error message. This micro-UX improvement ensures developers have accurate, context-aware visual feedback and don't get confused by lingering red/yellow backgrounds on unknown states.

📸 Before/After

Before: If the score fell below threshold (yellow background), and then a CLI error occurred, the status bar showed $(shield) CDD: ? but kept the yellow background. Error states were swallowed entirely.
After: Error states show $(error) CDD: Error with a red background and the error in the tooltip. Unknown states explicitly clear the background color.

♿ Accessibility

Improves cognitive accessibility by providing consistent, clear context for state changes via explicit tooltips, rather than relying solely on icons or potentially stale background colors.


PR created automatically by Jules for task 13486129242837321735 started by @raccioly

Added proper cleanup of status bar `backgroundColor` when resolving back to an unknown state, and added informative context/tooltips to error states instead of defaulting to unknown state without explanation. Also converted `activate` to an async function to fix an await syntax error.

Co-authored-by: raccioly <63126795+raccioly@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant