C# Doctor: Report error and warning counts separately in the status bar
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start by locating the C# Doctor status-bar reporting path and the severity data used for its results. Verify with a result set containing two errors and two warnings; done when the status bar shows 2 errors and 2 warnings rather than 4 errors.
Written by the indexing model from the issue text.
Description
Description
C# Doctor currently reports all detected problems as errors in the bottom status bar. When the results contain different severities, the aggregate counts should preserve those severities instead of classifying every problem as an error.
For example, when C# Doctor finds two errors and two warnings, the status bar currently reports four errors. It should report two errors and two warnings, consistent with VS Code's standard Problems indicators.
Expected behavior
- Error results contribute to the error count.
- Warning results contribute to the warning count.
- A result set containing two errors and two warnings displays 2 errors and 2 warnings in the bottom status bar.
Actual behavior
The same result set displays 4 errors and no warnings.
Screenshots
Current behavior: C# Doctor reports all four findings as errors in the status bar.
Reference: VS Code reports error and warning counts separately.
- Dominant language
- No language data
- Stars
- 321
- Forks
- 54
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/vscode-dotnettools
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
microsoft/vscode-dotnettools#3563 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/vscode-dotnettools#3560 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/vscode-dotnettools#3557 ·
-
AIEngineering
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/vscode-dotnettools#3286 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/vscode-dotnettools#2919 · 1 comment ·
All issues in microsoft/vscode-dotnettools
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hemilabs/ui-monorepo#2332 ·
-
Help-Wanted Needs-Triage Package-Update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/winget-pkgs#438662 ·
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
olcf/olcf-test-harness#278 · 1 comment ·