Why You Don't Trust Your Linter
summary
Claim: linters lose trust because of false positives and poor communication. Demonstrates elm-review fixes that prompt one change at a time, generate suppress JSON files to track allowed legacy issues, and contrasts that with eslint --fix which produces large opaque diffs. Explains root causes: missing project/type information, accidental vs essential configuration, and ineffective ignore mechanisms. Shows concrete remedies: richer messages with why/how to fix, supply cross-file/type data, prefer enforced rules over scattered disable comments.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:59Google Maps
- 4:04Linter
- 6:04Elm-review
- 6:56False positives
- 15:50Communication
- 20:22Automatic fixes
- 24:08Configuring linters
- 29:21Ignoring reports
- 41:08Summary
- 42:31Outro
