Pending rules should not be printed as warnings by default
See original GitHub issueHaving all the pending rules printed to the output as warnings is not a useful default in my opinion. It drowns out any other non-pending warnings, and encourages the developer to form a habit in ignoring the output in general. Since we already fails the lint when a pending rule become fixed, there is very little value in continuously reminding the developer about them in the mean time. I think they should be hidden by default, and a --verbose
flag or something can turn them on if desired.
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (11 by maintainers)
Top Results From Across the Web
warnings — Warning control — Python 3.11.1 documentation
The printing of warning messages is done by calling showwarning() , which may be overridden; the default implementation of this function formats the...
Read more >Case Number Assignment - Messages - FHA Connection - HUD
A case number has been assigned and appears in the FHA Case Number field of the General Information section. Print out the page...
Read more >AppSourceCop Analyzer Rules - Business Central
Id Title Category Default Severity
AS0002 Fields must not be deleted. Upgrade Error
AS0005 Fields must not change name Upgrade Error
AS0009 Key fields must not...
Read more >Warnings - Ads API - Google Developers
Warnings can be used in two scenarios: When a feature is scheduled to be deprecated, or a new validation rule is to be...
Read more >THE BLUEBOOK MADE EASY - Penn State Law
As the Bluebook notes, practitioners in a state court must refer to the court's local rules when determining whether to provide parallel citations....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ya, I think we can make them not warnings and then add a command line option to toggle that (or to just print out pending issues). Happy to help shepherd a PR forward that does this.
This has been addressed as part of the todo feature implementation.