-
Notifications
You must be signed in to change notification settings - Fork 120
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
cannot find first or last token in PlusOp node #425
Comments
(removing the "plus" from line 4 and using a simple string works fine). |
Might be related to bug #389. |
Thanks for the report! Here's the decaffeinate-parser output for a minified test case: repl. Looks to me like a decaffeinate-parser bug: it's parsing it as two |
Closes decaffeinate/decaffeinate#425 There was already some logic to distinguish between explicit `+` operations and implicit ones generated as part of string interpolation parsing, but that logic wasn't used in all places. Now, we also use it in `isInterpolatedString`, which avoids a problem where `+` was seen as a string interpolation in some cases.
Closes decaffeinate/decaffeinate#425 There was already some logic to distinguish between explicit `+` operations and implicit ones generated as part of string interpolation parsing, but that logic wasn't used in all places. Now, we also use it in `isInterpolatedString`, which avoids a problem where `+` was seen as a string interpolation in some cases.
Closes decaffeinate/decaffeinate#425 There was already some logic to distinguish between explicit `+` operations and implicit ones generated as part of string interpolation parsing, but that logic wasn't used in all places. Now, we also use it in `isInterpolatedString`, which avoids a problem where `+` was seen as a string interpolation in some cases.
Closes decaffeinate/decaffeinate#425 Closes decaffeinate/decaffeinate#194 There was already some logic to distinguish between explicit `+` operations and implicit ones generated as part of string interpolation parsing, but that logic wasn't used in all places. Now, we also use it in `isInterpolatedString`, which avoids a problem where `+` was seen as a string interpolation in some cases.
I am using decaffeinate 2.23.1. decaffeinate is crashing on my CoffeeScript input:
(repl)
The text was updated successfully, but these errors were encountered: