Using "match" as variable in pipeline rule causes uncaught exception

[dmuensterer]

Expected Behavior

The rule editor has a syntax checker. It should highlight all syntax errors.

Current Behavior

When defining a variable named match an uncaught backend exception is triggered.

Possible Solution

Fix syntax checking.

Steps to Reproduce (for bugs)

Create pipeline rule and define a variable named match. E.g.

rule "test"
when
    has_field("message")
then
    let match = to_string($message.message);
end