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
Describe the bug
If a string literal contains a newline character \n, the newline is escaped and returned as \\n.
"Hello\nWorld"
// "Hello\\nWorld"
The behavior is different if the newline character is stored in a string variable and the variable is referenced in the expression. In this case, the newline is not escaped.
x
// "Hello\nWorld"
To Reproduce
Steps to reproduce the behavior:
Evaluate the expression "Hello\nWorld"
Verify that the newline character is escaped
Expected behavior
A newline character in a string literal is not escaped. The string is returned in its original form.
Describe the bug
If a string literal contains a newline character
\n
, the newline is escaped and returned as\\n
.The behavior is different if the newline character is stored in a string variable and the variable is referenced in the expression. In this case, the newline is not escaped.
To Reproduce
Steps to reproduce the behavior:
"Hello\nWorld"
Expected behavior
A newline character in a string literal is not escaped. The string is returned in its original form.
Environment
1.15.0+
8.0.2+
: Inconsistent/unnecessary escaping of characters in inputs camunda#9859The text was updated successfully, but these errors were encountered: