It would be interesting for people working on different projects to have a way to :
1: Set up extensions for the all team to have an uniform configuration
2: Have different extensions on different projects
I think that having a list of extensions in the Workspace configuration could solve this.
Otherwise i'll just have to write an extension for it :-)
Good suggestions, we had discussions along these lines and this falls into the category of how to deal with many extensions and how to work with extensions in a team. This topic is on our 6 month roadmap.
Thanks @joaomoreno for report duplication
I would like to suggest that VSCode should just look at .vscode/extensions folder of the opened folder to read extension in addition to global .vscode/extensions
Over one year later, can we have some light on the current status of this issue?
As noted over at https://web.archive.org/web/20170211004013/https://code.visualstudio.com/updates/v1_6#_workspace-extension-recommendations you can now create .vscode/extensions.json... (learned about this thru https://github.com/Microsoft/vscode/issues/5559#issuecomment-260083912)
I want to be able to load and unload these on-demand based upon which project I'm in, however - https://github.com/Microsoft/vscode/issues/39272 is along those lines
I wanna force my team to use some linters, such like ikappas.phpcs because it can check if the code quality is enough before they make a PR. The merge won't happen anyway if PHPCS isn't satisfyied.
I would like to force the usage of EditorConfig.EditorConfig.
Do I think forcing some extension is bad?
It can be, but if they don't like working following the rules, they are free to suggest some change in the rules or work somewhere else.
@odahcam use tools like husky and git hooks to prevent the invalid commits.
That would be a nice feature to have. The Code editor will be more responsive, because will load from .vscode the extensions which we are needed for the workspace/project. Have in mind, that peoples uses VSCode for everything, so installing like 30 extensions to have PHP, TS, JS, etc, have performance impact.
With this method we can load extensions which we actually need.
@cgatian I do use husky but the errors dont show in the IDE so we need to run it thru the terminal to see the actual error. Any ideas how I can improve this?
This feature can be big thing. After this, VS can be so good as Eclipse or VIM! I hope this will be soon :crying_cat_face: Just imagine multiple workspace per project... or per active extension like "Git" workspace or "Diff" workspace... not only editor change... but whole workspace can supoprt your actual work!
Much better would be something like profile manager. When you start VSCode, you have the ability to select your environment and set it as default if you dont want select it every launch, also switching between them, creating new one and deleting other ones.
@TheAifam5 there is some experiment https://github.com/aaronpowell/vscode-profile-switcher ... but it's not so complex.
@scippio nah. it changes only configuration.... does not isolate environments.
@scippio Thank you! This extension allows you to create different profiles, each with its own settings and EXTENSIONS. So when switching to a Web Php project I can enable the "Web Php" profile, when doing college activities in C, I switch to the "C" profile.
@TheAifam5 I suggest you read README.md, specifically the topic EXTENSIONS, I left the link below:
https://github.com/aaronpowell/vscode-profile-switcher#extensions
Most helpful comment
Over one year later, can we have some light on the current status of this issue?