Struct HealthFindingAction 

pub struct HealthFindingAction {
    pub kind: HealthFindingActionType,
    pub auto_fixable: bool,
    pub description: String,
    pub note: Option<String>,
    pub comment: Option<String>,
    pub placement: Option<String>,
    pub target_path: Option<String>,
}

Suggested action attached to a ComplexityViolation.

Each complexity finding carries an array of these on the JSON wire (findings[].actions[]). The action selector in crates/cli/src/report/json.rs::build_health_finding_actions picks the primary action based on which thresholds triggered the finding and the bucketed coverage tier. See HealthFindingActionType for the full discriminant list.

note, comment, and placement are populated per-variant: refactor actions carry a note, suppress-line / suppress-file actions carry comment plus placement, and the coverage-leaning actions (add-tests, increase-coverage) carry only note.

Fields

kind: HealthFindingActionType

Action type identifier. A single finding’s actions array can carry MULTIPLE entries of different types: e.g., a finding that exceeded both cyclomatic and CRAP at coverage_tier: partial will get BOTH increase-coverage AND refactor-function, plus suppress-line. Consumers that select a single action should treat the FIRST non-suppress-{line,file} action as primary. add-tests is emitted when CRAP triggered the finding, the function has no test coverage (coverage_tier: none), and full coverage can bring CRAP below max_crap_threshold (cyclomatic < threshold, since CRAP bottoms out at CC at 100% coverage). increase-coverage is emitted when CRAP triggered the finding, some coverage exists (coverage_tier: partial or high), and full coverage can bring CRAP below max_crap_threshold; the description steers toward targeted branch coverage rather than scaffolding new tests. refactor-function is emitted when cyclomatic/cognitive triggered the finding, when full coverage still cannot bring CRAP below max_crap_threshold (cyclomatic >= threshold), or as a secondary action when cyclomatic is within 5 of the cyclomatic threshold AND cognitive is at or above max_cognitive_threshold / 2 (the cognitive floor suppresses false positives on flat type-tag dispatchers and JSX render maps where high cyclomatic comes from a single switch with near-zero cognitive load). suppress-file is emitted instead of suppress-line for synthetic Angular <template> findings on .html files, because line-suppression comments cannot be expressed in HTML; the comment field carries <!-- fallow-ignore-file complexity --> and placement is top-of-template.

auto_fixable: bool

Whether fallow fix can auto-apply this action. Today every health finding action is manual, but the field is non-singleton so a future auto-applier (e.g., an LLM-driven refactor-function worker) does not need a schema change.

description: String

Human-readable description of the action.

note: Option<String>

Additional context (e.g., the canonical CRAP formula, or a hint about which branch type to extract). Present on most action types; dropped only when the description carries the full ask.

comment: Option<String>

The inline comment to insert (e.g., // fallow-ignore-next-line complexity or <!-- fallow-ignore-file complexity -->). Present on suppress-line and suppress-file action variants.

placement: Option<String>

Where to insert the suppress comment (e.g., above-function-declaration, above-angular-decorator, above-component-worst-method, or top-of-template). Present on suppress-line and suppress-file action variants.

target_path: Option<String>

Project-relative path the action should target when the finding’s remediation lives in a different file from where the finding is anchored. Currently populated on the increase-coverage action for synthetic Angular <template> findings whose CRAP is inherited from the owning .component.ts: the action points at the component file (where the user actually adds tests) rather than the .html template (where the finding is anchored but which is not directly testable). Absent when the action’s target is the finding’s own file.

Trait Implementations

impl Clone for HealthFindingAction

fn clone(&self) -> HealthFindingAction

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for HealthFindingAction

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Serialize for HealthFindingAction

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.