FlowDrop Workflow Specification 1.0-draft

An explicit null at a higher priority wins

Sending null is a decision, not a silence. A node that emits null on a wire has said something, and what it said beats whatever the author saved.

The rule

Normative: this is the rule
  1. At every priority, a value counts as supplied when a key of the parameter's name is present, whatever that key's value.
  2. An explicit null therefore wins over any lower priority: a null delivered on a wire beats the author's saved config, and a null in the saved config beats the schema default.
  3. This holds identically however a workflow is executed.
Rule identifiers are permanent and are never renumbered. Each implementation publishes its own standing against these rules; this specification does not.spec 1.0-draft · CFG-7 · changed in spec 1.0