Skip to content

Mark untrusted workspaces as supported #139

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 20, 2023
Merged

Mark untrusted workspaces as supported #139

merged 1 commit into from
Sep 20, 2023

Conversation

code-asher
Copy link
Member

It seems that if you do not use any files in the workspace then you can set this as true.

This fixes an issue where you get "no view is registered with id" because the extension seems to be in a half-activated state where the activate function runs but the view does not exist. If you check the extension list you see that the extension is disabled due to workspace trust. It might be a bug in VS Code that only presents when an extension is using the onResolveRemoteAuthority:ssh-remote activation event.

Fixes #134

It seems that if you do not use any files in the workspace then you can
set this as true.

This fixes an issue where you get "no view is registered with id"
because the extension seems to be in a half-activated state where the
activate function runs but the view does not exist.  Probably a bug in
VS Code but we might as well support untrusted workspaces anyway.
@code-asher code-asher merged commit 535cda4 into main Sep 20, 2023
@code-asher code-asher deleted the asher/no-view-id branch September 20, 2023 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

No view is registered with id: myWorkspaces
2 participants