-
Notifications
You must be signed in to change notification settings - Fork 38
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
Ensure ~ operator converts to string #125
base: master
Are you sure you want to change the base?
Conversation
Ensure that the binary concatenation operator (~) always produces a string value. We do that by utilizing the string template syntax instead of the binary plus (+) operator in the transpiled code. To make the generated code more efficient and easier to read we'll also collapse sibling template literals into a single. fixes #123
@clivend could you take a look, please? |
) | ||
); | ||
} | ||
// path.replaceWithJS({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This can then be removed, right?
The correct Babel version includes spaces after { and before } when using template literal expressions.
hey @pago sorry I rarely check github notifications. I see that there are new tests for this operator that cover different scenarios, we should be good to go here :) |
hallo this is still open right? |
hallo all can we close this? |
Reference issue: #123
What changed in this PR:
Ensure that the binary concatenation operator (~) always produces a string value.
We do that by utilizing the string template syntax instead of the binary plus (+) operator
in the transpiled code.
To make the generated code more efficient and easier to read we'll also collapse
sibling template literals into a single.