cliffano / jazz / 28708265129

100%

push

github

Fix echo-text escape sequences broken by string escaping security fix (#17)

* Initial plan

* Fix foreach regression: process escape sequences in scanner echo state

The security fix in d1db791 added backslash escaping in _compileExpr for
ast.Str nodes, which inadvertently broke template text that used \n and
similar escape sequences. Previously, \n in template text was stored as
two chars (backslash + n) and compiled to "\n" in generated JS (a
newline). After the fix, the backslash was double-escaped to \\n,
outputting literal \n instead of a newline.

Fix: add escape sequence processing to _echoState() in scanner.js so
that \n, \r, \t, and \\ in template echo text are converted to their
actual character values. This ensures the compiler's escaping correctly
round-trips them to the proper JS escape sequences in generated code.

* Add unit tests for echo-state escape sequence handling in scanner

* Add CHANGELOG entry for echo-text escape sequence fix

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>

412 of 412 branches covered (100.0%)

Branch coverage included in aggregate %.

22 of 22 new or added lines in 1 file covered. (100.0%)

1826 of 1826 relevant lines covered (100.0%)

78.55 hits per line