From 07c1d159c31950ee287c863ab10d89c5e2654ffa Mon Sep 17 00:00:00 2001
From: Eric Snow <eric.snow@microsoft.com>
Date: Wed, 3 Mar 2021 09:10:49 -0700
Subject: [PATCH] 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).
---
 news/3 Code Health/15525.md | 14 ++++++++++++++
 package.json                |  1 +
 2 files changed, 15 insertions(+)
 create mode 100644 news/3 Code Health/15525.md

diff --git a/news/3 Code Health/15525.md b/news/3 Code Health/15525.md
new file mode 100644
index 000000000000..5c6b493102b0
--- /dev/null
+++ b/news/3 Code Health/15525.md	
@@ -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.
diff --git a/package.json b/package.json
index 15352bfacd6c..713073d16094 100644
--- a/package.json
+++ b/package.json
@@ -47,6 +47,7 @@
         "Machine Learning",
         "Notebooks"
     ],
+    "requiresWorkspaceTrust": "onStart",
     "activationEvents": [
         "onLanguage:python",
         "onDebugResolve:python",