Rules
FP814 · impact-uncertain
A change to a published unit depends on something flowpact cannot evaluate statically.
| Code | Name | Category | Default severity |
|---|---|---|---|
FP814 | impact-uncertain | Contracts | 🟡 warning |
Why it matters
For example a check name built from the triggering event, needs outputs or vars, or a matrix computed at runtime. flowpact cannot tell whether consumers see a different check name, so it does not count the change (impact.uncertain: fail counts it).
How to fix
Review the change by hand, or make the name static (a literal name: or one built only from matrix and inputs).
Configure
Change the severity (or turn the rule off) in .github/flowpact/flowpact.config.yml, by code or by name:
rules:
FP814: off
# or: impact-uncertain: errorExplain it in the terminal:
flowpact explain FP814