-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Is it time to deprecate the CLI report output? #1739
Comments
+💯 Personally, I never use the prettyprint CLI and find it cumbersome to author and maintain audits. Another positive is that it would remove a BUNCH of code and tests. |
+1 |
Has anyone started this? I can take some/all of the audits. |
I guess i technically already deprecated output=pretty in #1764. (Did so by making it non-default.) One can still use it.. I'm thinking the CI scenario is the most likely for it to be valuable. I'm not 100% on removing all support for pretty at this point, though I do think it'd be fine to stop investing in our pretty formatters (table, crit path, etc). Those aren't worth it for us to maintain (or keep). |
Personally I won't try to read the results of the CLI output and I always reach for the HTML report.
Maybe that should be the default setup?
Thoughts?
The text was updated successfully, but these errors were encountered: