BIND001: expression-syntax-error
Expression does not parse
| Code | BIND001 |
| Name | expression-syntax-error |
| Category | Bindings and expressions (BIND) |
| Default severity | error |
| Enabled by default | yes |
| Fix available | no |
| ign-lint equivalent | none |
What it does
Section titled “What it does”Parses every Ignition expression with the grammar of Ignition 8.3's own parser and reports the first syntax error, as the gateway would: expression bindings, expression-structure leaves, expression transforms, tag bindings in expression mode, query binding parameters, polling rates, map transform expressions, tag expressions, derived tag expressions and expression-bound tag and alarm properties.
Locations that may hold either an expression or a literal (tag history tag paths, HTTP binding URLs) are only treated as expressions when they parse, so they are never reported.
Why is this bad?
Section titled “Why is this bad?”An expression that does not compile never evaluates: the binding shows an
error quality, the tag reports Bad_Config. Nothing warns at save time.
Example
Section titled “Example”if({view.params.mode} == 'edit', "Save", "Edit")Use instead (Ignition has no ==):
if({view.params.mode} = 'edit', "Save", "Edit")Generated from the rule metadata by iglint generate-docs; iglint rule BIND001 prints the same page in the terminal. Source: docs/rules/BIND001.md.