We are experiencing an issue where Prism's parser does not correctly track encoding changes on string nodes…
We are experiencing an issue where Prism's parser does not correctly track encoding changes on string nodes…: a task in LegoFlow-SWE (Harbor dataset). The affected node types include StringNode , XStringNode (backtick strings), heredocs, character literals, string parts within interpolated…
The task
The affected node types include `StringNode`, `XStringNode` (backtick strings), heredocs, character literals, string parts within interpolated strings, and string elements inside list literals (`%W`, `%I`). There is currently no mechanism to convey whether a string’s encoding has been forced.
Part of Lego-X/LegoFlow-SWE.