FlowDrop Workflow Specification 1.0-draft

A trigger mapping value can be escaped as a literal

The rule

Normative: this is the rule
  1. In a trigger mapping, a value prefixed literal: or wrapped in matching single or double quotes is taken as the literal string it spells, and is not extracted from the context.
  2. The escape applies to trigger mappings only.

What it means

A mapping value that starts with literal:, or that is wrapped in a matching pair of quotes, never reaches the path evaluator at all — it is not a path that happens to resolve to a fixed string, it is never looked up in the context in the first place. The quotes themselves are stripped from what is delivered, so a mapping cannot deliver a quoted string literally; quoting is consumed entirely by the escape. This behaviour is scoped to trigger mappings: an ordinary path elsewhere is not read this way just because it starts with a matching pair of quote characters.

Example

Three mapping values, escaped three different ways, against the same context.

A mapping with three literal-escaped valuesinput
{"static_key": "literal:my_static_value", "quoted_value": "\"quoted string\"", "single_quoted": "'single quoted'"}

Each produces the string it spells — my_static_value, quoted string, single quoted — with the prefix or the quotes consumed; none is looked up in the context.

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