chore: fix mechanical ESLint findings in the frontend #24
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "robinp2000/chore/frontend-lint-mechanical"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Apply the ESLint autofixes for four rules and re-run Prettier:
prefer-const(34)@typescript-eslint/no-inferrable-types(5)@typescript-eslint/prefer-function-type(1)@typescript-eslint/consistent-indexed-object-style(1)Why
First of several PRs that bring
npm run lintto zero so that it can beenforced in CI. Only fixers without behavioral impact are applied here. The
other autofixers (
template/no-autofocus,use-lifecycle-interface,no-wrapper-object-types) were switched off for this run and follow separately.Tests
ng buildsucceeds.npm run format:checkpasses.npm run lintfindings: 132 -> 91.