🎨 Palette: Add context-aware tooltips to VS Code extension status bar#86
🎨 Palette: Add context-aware tooltips to VS Code extension status bar#86
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: Added context-aware tooltips to the VS Code extension status bar for "unknown" and "error" states during score refresh, and fixed an
asyncsyntax error on the top-levelactivatefunction.🎯 Why: When developers encounter a
?CDD score in the status bar, a generic tooltip ("Click to see CDD score details") doesn't explain what went wrong. Providing informative tooltips clarifies whether the output couldn't be parsed or if an execution error occurred, enhancing the CLI-to-editor feedback loop.📸 Before/After: N/A (Tooltips now explicitly mention parse errors or execution errors instead of default text).
♿ Accessibility: Improved cognitive accessibility by providing clear, context-dependent textual feedback rather than relying on ambiguous visual cues (
?).PR created automatically by Jules for task 5760976148415975845 started by @raccioly