forked from DonJayamanne/pythonVSCode
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Use extension.open instead of openExternal #15780
Copy link
Copy link
Closed
Labels
area-editor-*User-facing catch-allUser-facing catch-allarea-intellisenseLSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc.LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc.bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugpartner ask
Description
Metadata
Metadata
Assignees
Labels
area-editor-*User-facing catch-allUser-facing catch-allarea-intellisenseLSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc.LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc.bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugpartner ask
Type
Fields
Give feedbackNo fields configured for issues without a type.
From microsoft/vscode#111814
Related code:
vscode-python/src/client/languageServices/proposeLanguageServerBanner.ts
Line 24 in 3698950
In order to open the Pylance extension editor, you should invoke the
extension.opencommand instead of usingopenExternal.cc @aeschli