Original Post: Three things your linter shouldn’t tell you
Summary:
Grayson Hardaway from the engineering team at r2c introduces Bento, a new code check tool designed to streamline the use of linters by focusing only on essential checks. Unlike traditional linters that can bombard developers with numerous and sometimes unnecessary errors, Bento minimizes this noise by adhering to three key principles:
- Avoid Style Violations: Style checks are disabled by default as tools like Black and Prettier can handle formatting automatically.
- Exclude Unpopular Checks: Bento disables checks that are commonly turned off by the developer community. This includes many ESLint checks and specific Bandit checks that developers often find irrelevant.
- Eliminate "Bad Checks": Checks that have a high false-positive rate and low probability of identifying actual bugs are disabled. An example given is Bandit’s B105 check for hardcoded passwords, which was found to be noisy and not very useful in practice.
Bento’s approach ensures that developers only see relevant issues, saving valuable time. The tool continually evolves by evaluating feedback and improving based on real-world usage.
Developers can start using Bento by visiting Bento.dev, and r2c welcomes feedback through email or GitHub issues.
Go here to read the Original Post