Unused component inputs
What an unused-component-input finding of fallow dead-code means, why it matters and how to fix it.
What it reports
An Angular @Input() / signal input() / model() input is read nowhere in its own component.
Dead code explains how fallow finds it.
Why it matters
An Angular @Input() / signal input() / model() declared input that is read nowhere in its own component (neither the inline / external template nor the class body). The Angular compiler never flags a declared-but-unread @Input, and there is no @angular-eslint rule for it. Conservative: usage detection over-credits by design (a template sentinel ref, any class-body member access by that name, or a bare identifier read counts as used), and the whole component abstains on an unresolved extends heritage clause (a base class in another file may read the input). A model() is recorded as an input only. Default warn; suppress or remove the input. The check runs only when the project declares @angular/core.
Example
user-card.component.ts declares @Input() size: string (or size = input<string>()) but size is read nowhere in the template or the class body.
Fix
Remove the unused input, or read it in the template or class body. If the input is part of a deliberately-stable public component API, suppress the line with // fallow-ignore-next-line unused-component-input.
Facts
| Fact | Value |
|---|---|
| Issue type | unused-component-input |
| Rule id in SARIF output | fallow/unused-component-input |
| Command | fallow dead-code |
| Default severity | warn |
Config key in rules | unused-component-inputs |
| Filter option | --unused-component-inputs |
| Suppression comment | // fallow-ignore-next-line unused-component-input |
Fixable with fallow fix | No |
| Opt-in | No |