FlowDrop Workflow Specification 1.0-draft

Visual type is the node type's, and is offered where there is a choice

The rule

Normative: this is the rule
  1. A node's visual type comes from its node type, never from a declared schema.
  2. Where the node type supports more than one visual type, a reserved nodeType string property is written into the config schema (its enum the supported types, its default the node type's own visual type), and the same value is stored as that key's config default.
  3. This write is unconditional: it overwrites a declared property of the same name.

What it means

Nothing about a declared schema can change a node's visual type, and the nodeType selector is not injected the way the other reserved config properties are: SCH-21's reserved properties each back off when the schema already declares a property of that name, but this one does not. A node type whose own schema declares its own nodeType property loses it, silently, to the injected selector.

Example

A node type declares two supported visual types, default and gateway, with default as its own.

The enum of the injected nodeType propertywritten
["default", "gateway"]

Its default is default, and the same value is written as the node's own stored config under that same key, never under a separate type key.

The title of the nodeType property on a node type whose processor declares its ownoverwritten
"Visual Type"

The declared property's own title does not survive; the enum and default are the injected ones.

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