-
Notifications
You must be signed in to change notification settings - Fork 564
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: OS CLI output part I - update severity headline +test #3437
Conversation
) + | ||
reachabilityText + | ||
'\n ' + |
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.
Wondering you should use \t
instead of
to be more explicit, if the intention is for it to be tabbed?
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.
Looks good to me, left a comment that may or may not be relevant, commits also needs squashing prior to merge.
- Severity and Title should be the only content on the line, similar to the web/ide - [Severity] should be the first, in front of the title, similar to web/ide - Removing the word ‘severity’ and only keeping [Critical], [High], [Medium], [Low] - Proper color usage (e.g. Green shouldn’t be used for section titles)
5103fa8
to
305de41
Compare
Merge from branch 'master' into 'feat/os-cli-output+test'
d9f28cf
to
e7a7b04
Compare
🧹 Closing as stale. No activity in more than 1 year. |
What does this PR do?
Improve snyk-open-source CLI output as follows:
Where should the reviewer start?
src/lib/formatters/remediation-based-format-issues.ts
How should this be manually tested?
Run 'snyk test' command on a local project and compare output formatting with the attached screenshot
Any background context you want to provide?
What are the relevant tickets?
TUN-269
Screenshots
Additional questions