Skip to content
Fallow home
All docs pages

Docs home

Added suppressions

What an added-suppression finding of fallow audit means, why it matters and how to fix it.

What it reports

The change adds a suppression comment.

Changed code explains how fallow finds it.

Why it matters

fallow audit reports a comment line that the change adds with a lint, type-check, coverage or Fallow suppression: eslint-disable, oxlint-disable, biome-ignore, deno-lint-ignore, @ts-ignore, @ts-expect-error, @ts-nocheck, istanbul ignore, c8 ignore, v8 ignore or fallow-ignore. A moved comment is not added. A fallow-ignore comment that names only diff-risk rules does not count. Files below a fixture or generated directory (fixture, fixtures, __fixtures__, __snapshots__, generated, __generated__) do not report, because a tool writes them or a test reads them as data. Defaults to warn.

Example

A change adds // @ts-expect-error above a call instead of a correct type.

Fix

Decide if the suppression is necessary. If it is, keep it and suppress the finding with // fallow-ignore-next-line added-suppression, or turn the rule off for the path.

Facts

FactValue
Issue typeadded-suppression
Rule id in SARIF outputfallow/added-suppression
Commandfallow audit
Default severitywarn
Config key in rulesadded-suppression
Suppression comment// fallow-ignore-next-line added-suppression
Fixable with fallow fixNo
Opt-inNo