FlowDrop Workflow Specification 1.0-draft

A unified port's description skips trigger and hidden keys

The rule

Normative: this is the rule
  1. Both unified-port key enumerations skip the trigger port and every hidden parameter.
  2. A hidden port does not exist on the instance, so it never appears in a unified port's description.

What it means

Marking a parameter connectable does not put it in a unified port's description if that parameter is also trigger or hidden. The two gates are independent, and hidden wins: a node type can flag trigger and a hidden parameter connectable and the unified description still leaves them out, because a hidden port does not exist on the instance at all.

Example

A processor declares five parameters — trigger, two marked hidden (secret, ghost), and two ordinary ones (topic, mode) — and the node type marks every one but mode connectable.

The declared parameters, two marked hidden
{
  "trigger": { "x-data-type": "trigger" },
  "secret": { "type": "string", "format": "hidden" },
  "ghost": { "type": "string", "hidden": true },
  "topic": { "type": "string" },
  "mode": { "type": "string" }
}
The connectable keys enumerated for the unified input portenumerated
["topic"]

trigger, secret and ghost were all marked connectable; none of them enumerate.

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 · SCH-19 · changed in spec 1.0