Skip to content

🎨 Palette: [UX improvement] Add context-aware tooltips to VS Code extension error states#83

Draft
raccioly wants to merge 1 commit intomainfrom
palette-vscode-extension-ux-improvement-18254233441658972471
Draft

🎨 Palette: [UX improvement] Add context-aware tooltips to VS Code extension error states#83
raccioly wants to merge 1 commit intomainfrom
palette-vscode-extension-ux-improvement-18254233441658972471

Conversation

@raccioly
Copy link
Copy Markdown
Owner

@raccioly raccioly commented May 4, 2026

💡 What:
Added specific icons ($(warning) and $(error)), background theme colors (warningBackground and errorBackground), and dynamic tooltips to the VS Code status bar item when the CDD output fails to parse or when the underlying refresh command throws an exception.

🎯 Why:
Previously, the extension showed a generic $(shield) CDD: ? state when the CLI command completely failed or when the JSON output could not be parsed. This hidden failure state offered no clues to the user regarding the underlying problem. By making the status bar informative, developers immediately know what went wrong (e.g., an error parsing output or an exception thrown), preventing confusion and aiding in faster troubleshooting.

📸 Before/After:
Before: $(shield) CDD: ? with tooltip "Click to see CDD score details" regardless of whether the output was unparseable or errored out.
After:

  • Unparseable: $(warning) CDD: ? with yellow background and tooltip "Score unavailable - could not parse output."
  • Exception: $(error) CDD: Error with red background and tooltip "Error refreshing score: [e.message]."

♿ Accessibility:
Providing descriptive error messages via tooltips, along with distinct visual and icon changes, helps convey semantic meaning and context changes to screen readers and users navigating via keyboard, making the extension more accessible and transparent.


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

…atus bar errors

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