Stale suppressions
What a stale-suppression finding of fallow dead-code means, why it matters and how to fix it.
What it reports
Suppression comment or tag no longer matches any issue.
Suppress a finding explains how fallow finds it.
Why it matters
The comment tells readers that a problem exists where none does. When a new issue of the same kind appears on that line, the old comment hides it from review.
Example
// fallow-ignore-next-line unused-export stays above an export that another module imports, so no unused-export finding remains for the comment to suppress.
Fix
Remove the suppression. If a different issue is still intentional, replace it with a current, specific suppression.
Facts
| Fact | Value |
|---|---|
| Issue type | stale-suppression |
| Rule id in SARIF output | fallow/stale-suppression |
| Command | fallow dead-code |
| Default severity | warn |
Config key in rules | stale-suppressions |
| Filter option | --stale-suppressions |
Fixable with fallow fix | No |
| Opt-in | No |
Note. Fix by removing the stale suppression marker itself.
When to keep the code
- None. Remove the stale comment. A stale comment can hide a new finding at the same place later.
Notes
/** @expected-unused */marks an export that is unused on purpose. The tag becomes stale when code starts to use the export.- When a comment names an unknown issue type, fallow still applies the known names of that comment, and reports the unknown name as stale. Correct the name.