This repository has been archived by the owner on Mar 8, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 13
\n should not be parsed in strings #32
Labels
Comments
vmarkovtsev
changed the title
\n is parsed in strings
\n should not be parsed in strings
Aug 21, 2018
Blocked by bblfsh/sdk#318 |
@dennwc that should not block this issue. |
36 tasks
OK, I can confirm that it's unrelated to that issue. Usually, drivers provide an escaped (raw) string literal in the native AST. But for this driver, we used the unescaped value (parsed). I will change it to use the raw value in Native/Annotated and parse it for Semantic (like in all other drivers). |
dennwc
pushed a commit
to dennwc/javascript-driver
that referenced
this issue
Jan 3, 2019
Signed-off-by: Denys Smirnov <[email protected]>
dennwc
pushed a commit
to dennwc/javascript-driver
that referenced
this issue
Jan 3, 2019
Signed-off-by: Denys Smirnov <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Any JS string which has
\n
, e.g.contains parsed new lines instead of
\n
. The desired behavior is passing the string contents verbatim.The text was updated successfully, but these errors were encountered: