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

why do we need a vscode-resource schema #48512

Closed
dbaeumer opened this issue Apr 24, 2018 · 1 comment
Closed

why do we need a vscode-resource schema #48512

dbaeumer opened this issue Apr 24, 2018 · 1 comment
Assignees
@mjbvz
Labels
*as-designed Described behavior is as designed

Comments

@dbaeumer
Copy link
Member

Tests #48453.

It is unclear to me why we need a special vscode-resource schema. Couldn't this be normal file schemas.
@mjbvz
Copy link
Collaborator

mjbvz commented Apr 24, 2018

This is done for security reasons. We can better control and scope a custom scheme. Doing the same with the file: scheme is difficult, if not impossible

@mjbvz mjbvz closed this as completed Apr 24, 2018
@mjbvz mjbvz added the *as-designed Described behavior is as designed label Apr 24, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Jun 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@mjbvz mjbvz

Labels
*as-designed Described behavior is as designed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dbaeumer @mjbvz