Skip to main content

FUI1001: Component should use the canonical primitive

serious

Why Fragments emitted FUI1001 and how to resolve components/non-canonical.

Details

diagnostic
{
  "code": "FUI1001",
  "ruleId": "components/non-canonical",
  "category": "Canonical Usage",
  "defaultSeverity": "serious",
  "lifecycle": "experimental",
  "fixAvailable": true,
  "evidenceRequired": true
}

Guidance

## What it means

Fragments emitted `FUI1001` from `components/non-canonical` 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 check so `components/non-canonical` reflects the intended contract. Do not hide the finding with a broad repository exclude. When an exception is intentional, use a line-attached, reasoned directive from the [exceptions reference](/cloud/verdicts#in-source).

## 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 exception reference.

Next steps

  • RulesThe rules that emit FUI codes.
  • ExceptionsIn-source allows and Cloud exceptions.