Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Workspace Trust feature of VSCode #401

Open
kitsonk opened this issue Apr 23, 2021 · 3 comments
Open

Workspace Trust feature of VSCode #401

kitsonk opened this issue Apr 23, 2021 · 3 comments
Labels
enhancement New feature or request

Comments

@kitsonk
Copy link
Contributor

kitsonk commented Apr 23, 2021

This is a tracking issue for the upcoming feature for VSCode extensions (see: microsoft/vscode#120251 (comment)).
@kitsonk kitsonk added the enhancement New feature or request label Apr 23, 2021
@LeoDog896
Copy link
Contributor

Given that workspace trust is now merged, what would be some good places to implement the feature?

@bartlomieju
Copy link
Member

@LeoDog896 could you point me to a relevant API that provides this feature? I might be able to suggest a place to implement it then

@LeoDog896
Copy link
Contributor

API Docs are in the extension guide. Given deno's innate security policy, I'm not sure where the deno extension should revoke access for restricted workspaces.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kitsonk @bartlomieju @LeoDog896