You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the expressions language has some "gotchas" that aren't documented. Additionally, expected data types for the fields that expr can be used with are not declared.
Currently, expressions using matches (regex) cannot have named capture groups in them. This makes sense, but isn't documented, and can catch people trying to make a router by copy/pasting the regex from a regex_parser that the router will drive to.
Additionally, all escape characters (backslash by default), but be escaped. This is counterintuitive, as it does not match out regex_parser.
Non-working example (contains named capture groups, and does not escape the escape characters)
Currently the expressions language has some "gotchas" that aren't documented. Additionally, expected data types for the fields that expr can be used with are not declared.
Currently, expressions using matches (regex) cannot have named capture groups in them. This makes sense, but isn't documented, and can catch people trying to make a router by copy/pasting the regex from a regex_parser that the router will drive to.
Additionally, all escape characters (backslash by default), but be escaped. This is counterintuitive, as it does not match out regex_parser.
Non-working example (contains named capture groups, and does not escape the escape characters)
Working version of the above
Data that matches the formatA
The text was updated successfully, but these errors were encountered: