-
Notifications
You must be signed in to change notification settings - Fork 291
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 setting for supporting pylance handling notebook intellisense #8140
Conversation
private onDidChangeConfiguration(event: ConfigurationChangeEvent) { | ||
if ( | ||
event.affectsConfiguration('jupyter.pylanceHandlesNotebooks') || | ||
event.affectsConfiguration('python.languageServer') |
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 probably doesn't matter, but feasibly someone could change from "Pylance" to "Default" or vice versa, in which case the config changes from VS Code's view, but under the hood, the Python extension does nothing.
I doubt it really matters, but thought I'd mention.
Codecov Report
@@ Coverage Diff @@
## main #8140 +/- ##
=====================================
- Coverage 71% 71% -1%
=====================================
Files 366 366
Lines 22689 22606 -83
Branches 3445 3418 -27
=====================================
- Hits 16266 16197 -69
+ Misses 5012 5010 -2
+ Partials 1411 1399 -12
|
* Update package.json For #8140 * Fixup mock problem and ensure intellisense uses pylance in devmode * Fix host types * Fix metadata not being visible
Fixes #8076
Modify creation of the middleware portion to use the 'pylance' middleware based on a setting. Prerequisite for pylance to start on their own version of notebook intellisense