Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Newline characters should not be escaped #701

Closed
saig0 opened this issue Aug 28, 2023 · 0 comments · Fixed by #750
Closed

Newline characters should not be escaped #701

saig0 opened this issue Aug 28, 2023 · 0 comments · Fixed by #750
Assignees
Labels
scope: Camunda 8 Required in the context of Camunda 8 type: bug

Comments

@saig0
Copy link
Member

saig0 commented Aug 28, 2023

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:

  1. Evaluate the expression "Hello\nWorld"
  2. 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.

"Hello\nWorld"
// "Hello\nWorld"

Environment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: Camunda 8 Required in the context of Camunda 8 type: bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants