3 ms·
Typescript lints are type-aware so you can’t just lint changed files, you have to relint the entire codebase to check if any type changes have impacted the unch
by throwup238 3y ago
Typescript lints are type-aware so you can’t just lint changed files, you have to relint the entire codebase to check if any type changes have impacted the unchanged code.
- pcthrowaway 3y agoWouldn't an issue with a type change be caught at typescript compile/check steps? I'm not aware of eslint rules which would complain about some other untouched file if types have changed in ways such that the program still compiles
- anamexis 3y agoA few examples of typescript-eslint rules that could fail when a type in another file is changed: https://typescript-eslint.io/rules/await-thenable/ https://typescript-eslint.io/rules/await-thenable/ https://typescript-eslint.io/rules/no-for-in-array https://typescript-eslint.io/rules/no-for-in-array https://typescript-eslint.io/rules/no-duplicate-type-constituents https://typescript-eslint.io/rules/no-duplicate-type-constit...
- Too 3y agoIs there no incremental lint mode? When developing you need that for instant feedback, same mechanism should work for CI.