Skip to main content

trigger_is_ported

Function trigger_is_ported 

Source
pub fn trigger_is_ported(trigger: Trigger) -> bool
Expand description

What: Whether this executable implements the lifecycle a trigger belongs to. Why: Every lifecycle is ported: the exhaustive match below answers true for each variant, and a new variant fails to compile until it is answered here. The engine still checks this before running a lifecycle, so a future unported variant gets a typed “unavailable” instead of running zero policies and looking clean.

In TS you’d write (pseudocode):

const ported = (trigger: Trigger): boolean => true;