Automated consistency.
WHAT A FORMATTER DOES
Applies consistent formatting automatically.
WHY IT MATTERS
Style stops being discussed, and review addresses substance only.
WHAT TO CONFIGURE
Formatting on save, and on commit.
WHAT A LINTER DOES
Flags likely errors and discouraged patterns.
WHAT TO ENABLE
The recommended rules for your framework Accessibility rules, where available Rules catching genuine errors
WHY ACCESSIBILITY RULES
They catch a meaningful proportion of failures automatically.
WHAT NOT TO ENABLE
Rules that are matters of taste, and generate noise.
WHY
Warnings people ignore train them to ignore warnings.
WHAT TYPE CHECKING ADDS
Errors caught before running.
WHAT TO RUN AUTOMATICALLY
Formatting, linting, type checking and tests, on every change.
WHERE
In a pipeline, and locally before commit.
WHAT TO DO ABOUT EXISTING PROJECTS WITH MANY VIOLATIONS
Fix formatting in one commit, separately from behaviour changes Adopt rules gradually
WHY SEPARATELY
Otherwise the real change is invisible among reformatted lines.
