From 7b2b79a0466c62bd18f9e10d6c6acd0ed33bcb35 Mon Sep 17 00:00:00 2001
From: Jasper Hugunin <jasper@hugunin.net>
Date: Wed, 21 Feb 2024 18:20:06 -0800
Subject: [PATCH] Allow the extension to be active in untrusted workspaces

Closes #305

Just ran into this today. At an absolute minimum, the language definition and grammar should be available even in untrusted workspaces, but a quick look suggests that the generate command is also safe. There is no substitution in the template, plus the user would have to run the command manually. At worst, untrusted files could set their own `.editorconfig`, which only applies to files below in the directory hierarchy: This is probably wanted behavior even in an untrusted workspace.
---
 package.json | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/package.json b/package.json
index 1d3711f..8c237f4 100644
--- a/package.json
+++ b/package.json
@@ -98,6 +98,9 @@
     "virtualWorkspaces": {
       "supported": false,
       "description": "The `editorconfig` dependency requires fs access for parsing the config to use."
+    },
+    "untrustedWorkspaces": {
+      "supported": true
     }
   },
   "dependencies": {