-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add Pylance
setting and prompt for install if Pylance extension is missing
#13123
Conversation
Codecov Report
@@ Coverage Diff @@
## master #13123 +/- ##
==========================================
- Coverage 59.79% 59.62% -0.17%
==========================================
Files 671 670 -1
Lines 36681 36835 +154
Branches 5158 5189 +31
==========================================
+ Hits 21933 21963 +30
- Misses 13655 13777 +122
- Partials 1093 1095 +2
Continue to review full report at Codecov.
|
One other thing that would be good to do: Right now, for people without Pylance installed, it's going to be two reloads because the process is like:
Can the first step be modified to say "if changing to Pylance and Pylance not installed, load pylance banner instead"? That way you only have the one reload to actually finish the whole process. |
Basically activator and change settings tracker should be calling the same code that would check if Pylance is installed. So the code needs to move from activator into some shared class. |
Some of it, anyway. Three lines to do |
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.
Behavior looks good to me.
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
For #13122
Add
Pylance
setting topython.languageServer
Check if Pylance is installed and prompt for install if it is missing
Related tests
Add few strings to localization
Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
Title summarizes what is changing.
Has a news entry file (remember to thank yourself!).
Appropriate comments and documentation strings in the code.
Has sufficient logging.
- [ ] Has telemetry for enhancements.- [ ] Test plan is updated as appropriate.- [ ]package-lock.json
has been regenerated by runningnpm install
(if dependencies have changed).- [ ] The wiki is updated with any design decisions/details.