FlowDrop Workflow Specification 1.0-draft

A pattern mismatch is refused, a broken pattern is not

A pattern the implementation cannot compile is a defect in the node type, not in the workflow, and the author who cannot fix it must not be blocked by it.

The rule

Normative: this is the rule
  1. A string config value that does not match its schema's pattern is refused with R6_CONFIG_INVALID at node.{id}.config.{key}.
  2. Where the pattern itself is not a valid expression, the value is not refused: the workflow is accepted and no error is charged to the author.

What it means

A pattern that does not compile is treated the opposite way from a value that does not match one: a mismatch refuses the value, but a pattern the implementation cannot even evaluate refuses nothing. The schema is at fault there, not the value offered against it, so the author is not the one who pays for it.

Example

The value assigned to a key requiring an https prefixrefused
"ftp://example.com"
The value assigned to a key whose own pattern cannot compileaccepted
"anything at all"
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.h · changed in spec 1.0