Skip to content
Fallow home
All docs pages

Docs home

Boundary coverage

What a boundary-coverage finding of fallow dead-code means, why it matters and how to fix it.

What it reports

Source file matches no configured architecture boundary zone.

Architecture explains how fallow finds it.

Why it matters

A file outside every zone is outside every boundary rule, so it can import from any layer. New code in that file can break the architecture, and no check reports it.

Example

src/generated/client.ts is reachable but does not match any boundaries.zones[].patterns entry.

Fix

Add the file to the intended zone pattern, move it under a zoned directory, or add a generated-file glob to boundaries.coverage.allowUnmatched.

Facts

FactValue
Issue typeboundary-coverage
Rule id in SARIF outputfallow/boundary-coverage
Commandfallow dead-code
Default severityerror
Config key in rulesboundary-violation
Filter option--boundary-violations
Suppression comment// fallow-ignore-file boundary-violation
Fixable with fallow fixNo
Opt-inNo

Note. Requires boundaries.coverage.requireAllFiles.