You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VS Code now has the workspace trust feature which requires a workspace to be trusted before working in it. Upstream VS Code does have a command line option --disable-workspace-trust to disable this feature:
have no effect since VS Code settings in the main are stored in the browser now and file based settings aren't used.
The ask is for a way to be able to disable workspace trust mechanism from the command line when running code-server.
Why do you want this feature?
Am embedding code-server in another hosted web application where precisely controlling what files are available and users needing to trust the workspace is not a great workflow and is unnecessary.
Further, we are using a VS Code extension which allows remote API access to automate actions in VS Code from the web application code-server is embedded in, such as open a file, but this extension's workflow is broken by the workspace trust feature because a file cannot be opened via the remote API until the workspace is trusted.
Are there any workarounds to get this functionality today?
No idea.
Are you interested in submitting a PR for this?
I have no knowledge on how it would be added.
The text was updated successfully, but these errors were encountered:
What is your suggestion?
VS Code now has the workspace trust feature which requires a workspace to be trusted before working in it. Upstream VS Code does have a command line option
--disable-workspace-trust
to disable this feature:but the same option is not available in
code-server
. Further, adding settings to:such as:
have no effect since VS Code settings in the main are stored in the browser now and file based settings aren't used.
The ask is for a way to be able to disable workspace trust mechanism from the command line when running code-server.
Why do you want this feature?
Am embedding code-server in another hosted web application where precisely controlling what files are available and users needing to trust the workspace is not a great workflow and is unnecessary.
Further, we are using a VS Code extension which allows remote API access to automate actions in VS Code from the web application code-server is embedded in, such as open a file, but this extension's workflow is broken by the workspace trust feature because a file cannot be opened via the remote API until the workspace is trusted.
Are there any workarounds to get this functionality today?
No idea.
Are you interested in submitting a PR for this?
I have no knowledge on how it would be added.
The text was updated successfully, but these errors were encountered: