rule-no-lint-suppress

To prevent eslint-disable and @ts-ignore comments in your TypeScript codebase, enforce a no-suppression rule across CI and development workflows. This requires explicit handling of lint and TypeScript errors, prompting developers to fix root causes instead of silencing issues.

Banning lint suppression directives prevents hidden bugs and technical debt. When developers use comments like eslint-disable or @ts-ignore, they mask underlying issues; requiring explicit fixes ensures higher-quality changes and maintains coding standards.

The best way to enforce no error suppression in CI pipelines is to apply a no-lint-suppress rule that blocks code containing suppression directives. This guides developers to safely remediate issues or adjust lint configurations before merging code.

To fix TypeScript errors without suppression comments, address the root cause directly by correcting type definitions or logic. If the error is a false positive, adjust the TypeScript or ESLint configuration rules appropriately rather than silencing the warning.

Yes, you can integrate a no-suppression rule with your existing static analysis workflow. It applies across both CI and local development environments to ensure lint and TypeScript errors are addressed rather than silenced during code reviews.

When a teammate pushes code with an eslint-disable comment, the no-suppress rule triggers a prompt for code fixes. It blocks the suppression directive and guides the developer toward addressing the underlying issue to ensure higher-quality changes.