A condition node's operators are a closed set, and case folding spares the pattern
The rule
Normative: this is the rule
- A condition node compares with exactly six operators (
equals,not_equals,contains,starts_with,ends_withandregex) declared as an enumeration. - A workflow naming an operator outside that set is refused when it is saved and again when the parameter is resolved, and an operator that reaches execution outside the set fails the node.
- A pattern that cannot be compiled fails the node when it runs.
- Where the comparison is case-insensitive it is performed case-insensitively.
- For
regexthe pattern text is never rewritten: case insensitivity is applied as the regular-expression engine's own case-insensitive mode, so every escape the author wrote keeps the meaning they gave it and a pattern written to match non-digits does not come to match digits. - A character class in the pattern folds along with the rest of the comparison, because that is the case-insensitive comparison the author asked for.
Why
Recorded under OPEN-19.
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-28 · changed in spec 1.0