The Go implementation of TagExpressions escapes parentheses even if there are other characters between the backslash and the parentheses

[yusuke-noda]

Describe the bug
The Go implementation of TagExpressions escapes parentheses even if there are other characters between the backslash and the parentheses, such as (@foo or @\bar)

Expected behavior
Only the parentheses immediately after the backslash are escaped.

expr1, err1 = Parse("(@foo or @\bar)") // success
expr1.Evaluate([]string{"@bar"}) // return true
expr2, err2 = Parse("@foo or @\bar)") // return error "Syntax error. Unmatched )"

Current behavior
The parentheses are escaped even if there are other characters between the backslash and the parentheses.

expr1, err1 = Parse("(@foo or @\bar)") // should success, but return error "Syntax error. Unmatched ("
expr2, err2 = Parse("@foo or @\bar)") // should return error "Syntax error. Unmatched )", but success
expr2.Evaluate([]string{"@bar"}) // return false
expr2.Evaluate([]string{"@bar)"}) // return true

Your Environment

• Tag Expressions 4.0.0

[aurelien-reeves]

Thanks for the report!

Please note that this issue may be moved to https://github.com/cucumber/tag-expresssions soon