-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
support for template strings with replacement expressions #2111
Conversation
🦋 Changeset detectedLatest commit: 3aa6c6d The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest changes of this PR are available as canary in npm (based on the declared
|
Codecov Report
@@ Coverage Diff @@
## main #2111 +/- ##
==========================================
- Coverage 65.70% 64.78% -0.93%
==========================================
Files 85 77 -8
Lines 5106 5185 +79
Branches 1631 1654 +23
==========================================
+ Hits 3355 3359 +4
- Misses 1747 1822 +75
Partials 4 4
Continue to review full report at Codecov.
|
1d59e2a
to
48a44d9
Compare
this adds support for template strings with variable replacement expressions. they will be replaced by a blank whitespace chracter. characters *will* be off for the same line
48a44d9
to
3aa6c6d
Compare
this adds some support for template strings with variable replacement expressions. this should remove the validation error for EOL. completion and hover should work for all segments of the template literal expression as well
the expressions will be replaced by a blank whitespace character.
characters will be off for the same line, so it won't work everywhere, and if replacing the template string expression still breaks parsing because of how its used, there isn't much else we can do