-
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
LSP Server should parse more JS extensions #2060
Conversation
🦋 Changeset detectedLatest commit: 2442543 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 #2060 +/- ##
==========================================
- Coverage 65.70% 63.34% -2.37%
==========================================
Files 85 94 +9
Lines 5106 5442 +336
Branches 1631 1715 +84
==========================================
+ Hits 3355 3447 +92
- Misses 1747 1990 +243
- Partials 4 5 +1
Continue to review full report at Codecov.
|
There are a bunch more extensions people are using these days for javascript so it's time to honor them. This *should* fix #1955 when published to `vscode-graphql`, though graphql shouldn't be trying to parse those files anyways, so a bit more digging is in order
dc6db4c
to
0eef383
Compare
There are many more extensions people are using these days for javascript so it's time to honor all of them. This should fix #1955 when published to
vscode-graphql
, though graphql shouldn't be trying to parse those files anyways, so a bit more digging is in order