Summary
Transition from a dashboard-only view to an "inline" experience where the extension highlights inefficient code patterns directly in the code editor.
Problem
Currently, users have to leave their code and open the dashboard to see results. This breaks the developer's flow and makes it harder to identify exactly which line of code needs optimization.
Proposed solution
Use VS Code's Diagnostic API to underline specific code blocks (like deep nested loops or heavy libraries imports). When a user hovers over the underlined code, a tooltip should explain the carbon impact and suggest an alternative.
Acceptance criteria
Additional context
Similar to how ESLint works. We want to guide the developer while they are typing.
Summary
Transition from a dashboard-only view to an "inline" experience where the extension highlights inefficient code patterns directly in the code editor.
Problem
Currently, users have to leave their code and open the dashboard to see results. This breaks the developer's flow and makes it harder to identify exactly which line of code needs optimization.
Proposed solution
Use VS Code's
DiagnosticAPI to underline specific code blocks (like deep nested loops or heavy libraries imports). When a user hovers over the underlined code, a tooltip should explain the carbon impact and suggest an alternative.Acceptance criteria
vscode.languages.createDiagnosticCollection.Additional context
Similar to how ESLint works. We want to guide the developer while they are typing.