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.

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

Store information about locally enabled/disabled extensions in .vscode folder #54823

Closed
FancyBanana opened this issue Jul 22, 2018 · 3 comments
Closed
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) extensions Issues concerning extensions

Comments

@FancyBanana
Copy link
Contributor

Currently it seems that information about which extension is enabled/disabled is stored globally.
I propose that workspace enabled/disabled state should be stored in .vscode folder. This way the configuration will survive moving/copying project folder to another location.

@vscodebot vscodebot bot added the extensions Issues concerning extensions label Jul 22, 2018
@burtek
Copy link

burtek commented Jul 23, 2018

Please keep in mind, that if implemented, the state should be kept in a separate file that could be explicitly ignored within VCS, so that it won't be shared between developers working on the same project. Especially, it should not be put in extensions.json, as this file may contain extensions recommendations that are usually included to VCS and shared between developers

@sandy081
Copy link
Member

Duplicate of #40239

Please provide your requirements/use cases in the other issue.

@sandy081 sandy081 added the *duplicate Issue identified as a duplicate of another issue(s) label Jul 24, 2018
@vscodebot
Copy link

vscodebot bot commented Jul 24, 2018

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Jul 24, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Sep 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) extensions Issues concerning extensions
Projects
None yet
Development

No branches or pull requests

3 participants