FUI1002: Preferred component should be used
seriousWhy Fragments emitted FUI1002 and how to resolve components/preferred-component.
Details
{
"code": "FUI1002",
"ruleId": "components/preferred-component",
"category": "Canonical Usage",
"defaultSeverity": "serious",
"lifecycle": "experimental",
"fixAvailable": true,
"evidenceRequired": true
}Guidance
What it means
Fragments emitted FUI1002 from components/preferred-component because the scanned source conflicts with an active canonical-usage contract rule. The finding location and evidence identify the exact authored input that was evaluated.
How to resolve it
Review the finding evidence, then change the source or the documented governance mechanism so components/preferred-component reflects the intended contract. Do not hide the finding with a broad repository exclude. When an exception is intentional, use a line-attached, reasoned suppression from the configuration reference.
Verify the change
Run npx @usefragments/cli check --changed --format agent, inspect the resulting evidence, and then run npx @usefragments/cli check --changed --ci. If the finding changes identity, review baseline churn instead of silently regenerating the baseline.
Intentional exception? Use a narrow, reasoned directive from the in-source suppression reference.