The V.S. Code team released "Workspace Trust Feature" in the May v1.57.1 update, and then they updated it 3-4 weeks later in the "June v1.58.1" update. As it isn't important I won't go into details about what it does, but I will say I am happy that they implemented it. They only issue I have had is trying to figure out the extensions that it disables when it disables them.
"Workspace Trust" works in a tree-hierarchy type of system, for example:
"If your root directory is trusted, all the files & directories in your root-directory will be trusted too, unless you configure Workspace Trust to do something else. Also there are exceptions, like dependencies, and folders like
node_modules, which doesn't seem to be trusted when the root directory is.".
Configuring my projects to be trusted is easy, as I just explained above, however; when I am in a project that isn't trusted, like when I download an extension, and I want to view the content first, half my extensions seem to not work, as they are disabled, and it doesn't say anywhere which ones are. This causes errors, and frustration.
So what I would like to know, is if there is anyway to tell when "Workspace trust" is disabling an extension?
I assume there has to be a better way, than waiting to use the extension, just to find out the directory is not trusted.
