forked from DonJayamanne/pythonVSCode
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Declare "Trusted Workspaces" support. (#15521)
(closes #15525) This change enables the new "Trusted Workspaces" feature of VS Code (see microsoft/vscode#106488) for the extension. For now a user must put `"workspace.trustEnabled": true` in their settings.json to trigger the functionality (and it only works on VS Code insiders).
- Loading branch information
1 parent
5e82a6b
commit 07c1d15
Showing
2 changed files
with
15 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
Add support for "Trusted Workspaces". | ||
|
||
"Trusted Workspaces" is an upcoming feature in VS Code. (See: | ||
https://github.com/microsoft/vscode/issues/106488.) For now you need | ||
the following for the experience: | ||
|
||
* the latest VS Code Insiders | ||
* add `"workspace.trustEnabled": true` to your user settings.json | ||
|
||
At that point, when the Python extension would normally activate, VS Code | ||
will prompt you about whether or not the current workspace is trusted. | ||
If not then the extension will be disabled (but only for that workspace). | ||
As soon as the workspace is marked as trusted, the extension will | ||
activate. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters