Skip to content
Fallow home
All docs pages

Docs home

Boundary calls

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

What it reports

Zoned file calls a callee its zone forbids.

Architecture explains how fallow finds it.

Why it matters

The zone now performs an effect that the architecture keeps out of it, such as a shell command in domain code. Its tests then need that effect, and reviewers of the zone do not expect it.

Example

src/domain/policy.ts calls execSync from node:child_process while boundaries.calls.forbidden bans child_process.* from the domain zone.

Fix

Move the call into a zone that may perform the effect, route it through an allowed abstraction, or narrow the forbidden pattern if the rule was wrong. To suppress, use the boundary family token: // fallow-ignore-next-line boundary-violation governs import, coverage, and call findings alike (the rule-id-shaped boundary-call-violation is accepted as an alias).

Facts

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

Note. Requires boundaries.calls.forbidden patterns.