-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: support severity threshold #155
Conversation
thisislawatts
commented
May 6, 2024
- refactor: rename to remove typo
- feat: filter findings output to remove items outside of target severity
- fix: load severity-threshold from configuration
- feat: filter output by supplied severity threshold
if !satisfyMinLevel { | ||
openIssueLabelledCount += renderInSeverityColor(severity, fmt.Sprintf(" %d %s ", 0, strings.ToUpper(severity))) | ||
ignoredIssueLabelledCount += renderInSeverityColor(severity, fmt.Sprintf(" %d %s ", 0, strings.ToUpper(severity))) | ||
continue |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: Design decision will be needed on whether we want to show 0 LOW
when in fact there were Low Issues but they have been filtered out by --severity-threshold
setting.
CLI-304
1d67ff4
to
94f9262
Compare
Following a review session earlier today with @PeterSchafer we agreed to refactoring snyk/cli#5220, into GAF. |
} | ||
|
||
return reversed | ||
return original | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
praise: Nice optimisation