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

Please add a configuration file to control which extensions are enabled or disabled #82299

Closed
GWIian opened this issue Oct 11, 2019 · 3 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@GWIian
Copy link

GWIian commented Oct 11, 2019

Overall, vscode is great, and I'd like you to add a new feature: for extensions, you can have a special configuration file under the.vscode folder to control which plug-ins you need to enable for the project itself. Plug-ins not in the list are automatically disabled in the workspace, plug-ins in the list are automatically enabled, and uninstalled plug-ins can be automatically installed. I thought it would be cool and we could make sure that all the plug-ins we enabled were needed for the project.

@vscodebot
Copy link

vscodebot bot commented Oct 11, 2019

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

@sandy081 sandy081 added the *duplicate Issue identified as a duplicate of another issue(s) label Nov 17, 2019
@vscodebot
Copy link

vscodebot bot commented Nov 17, 2019

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 Nov 17, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 1, 2020
@sandy081
Copy link
Member

sandy081 commented Mar 4, 2024

Duplicate of #18386

@sandy081 sandy081 marked this as a duplicate of #18386 Mar 4, 2024
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)
Projects
None yet
Development

No branches or pull requests

2 participants