FlowDrop Workflow Specification 1.0-draft

The reserved config properties every node carries

The rule

Normative: this is the rule
  1. instanceTitle and instanceDescription are injected into every node's config schema; maxRetries and ports into an executable node's config schema only.
  2. Each injection is skipped where the node type already declares a property of that name.

What it means

The skip is per property, not all-or-nothing. A node type that declares its own instanceTitle keeps that declaration untouched, but still gets instanceDescription, maxRetries and ports injected alongside it — the declaration does not opt the node out of the other three.

Example

A node type declares its own instanceTitle, with a custom title and group, and its own maxRetries, with a custom title and default of 5.

What the config schema carries after injectionkept
{
  "instanceTitle": { "type": "string", "title": "Custom Title", "x-group": "execution" },
  "maxRetries": { "type": "integer", "title": "Custom Retries", "default": 5 }
}

Both declared properties come through unchanged, and instanceDescription and ports are injected beside them all the same.

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