VSCode should surface `BestPractice` or `ManualReview` severity rules in problems window
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1k
- Forks
- 131
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Describe the bug
Only hits from custom rules with severity: moderate and severity: critical show up in VS code.
To Reproduce
All are selected:
The problems tab shows low/note problems from other linters but not from DevSkim:
Expected behavior
severities: critical (red), moderate (yellow), low (blue). And a fallback to blue for unsupported keys because otherwise they won't show at all in VScode.
Versions(please complete the following information):
- OS: Windows 11
- devskim 1.0.44+10b85ce690
Additional context
I tried the others I found, none show a blue I icon at note/low level:
"low",
"medium",
"high",
"critical",
"moderate",
"important",
"manualreview",
"bestpractice",
"unspecified",
"Critical",
"ManualReview",
"BestPractice"
Contributor guide
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.
Research direction
Reproduce the issue in the DevSkim VS Code integration using custom rules with the listed severity values, then locate the diagnostic severity mapping used for the Problems window. Done means critical, moderate, and low severities appear with the expected colors, while unsupported values fall back to blue instead of being omitted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, vscode
- Domain
- devtools, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100