Closed valentine195 closed 6 months ago
I believe this is due to the grammar checking against Is first, which causes a failure due to an unexpected character:
{ "source": "request.verb IsNot \"GET\"", "line": 327, "column": 17, "message": "Condition expression is invalid. Position 16, SyntaxError: Expected [ \\t\\n] but \"N\" found.", "ruleId": "CC007", "severity": 2, "nodeType": "Condition" }
Ack. Until we push a fix, can you use != until then?
!=
@ssvaidyanathan I just reversed the equality/inequality grammar locally, no worries.
fixed and released in v2.48.0
I believe this is due to the grammar checking against Is first, which causes a failure due to an unexpected character: