FlowDrop Workflow Specification 1.0-draft

Required config keys must be present

The list of required keys is the one the node type's derived config schema publishes, not the node type's raw required flags; a parameter that can be fed by an edge is deliberately not required in config.

The rule

Normative: this is the rule
  1. Every key the node's derived config schema marks required must be present in the node's config.
  2. A key present with the value null counts as present.
  3. Each missing key yields one R6_CONFIG_REQUIRED at node.{id}.config.{key} (where {id} is the node's id and {key} the missing key), and the save does not take effect.
  4. A parameter the node type also marks connectable does not appear on the derived required list, so its absence from config is accepted at save even when no edge supplies it; the omission is decided from the node type's declared flags and never from the workflow's actual edges.
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 · R6.b · changed in spec 1.0