Ability to enable only [all] recommended extensions

[n3rd4i]

The ability to only enable the recommended extensions for the specific workspace [folder].

[sandy081]

@n3rd4i Do you mean to install or enable them only for the workspace that has recommendations?

[n3rd4i]

Do you mean to install or enable them only for the workspace that has recommendations?

Sort answer, maybe both.

1. Enable them (if they are disabled) for the workspace where they are recommended.
   1.1 But to be able to do so with one command (enable recommended extensions) like:
   -- e.g. Existing command: Enable Auto Updating Extensions (which maps to internal command)
   -- New command in that listing: Enable Recommended Extensions (which should map to internal command)
2. Additionally, It would be helpful if they where also installed if they are not there already.
3. Also, always when extensions are installed, they are enabled globally, never they are enabled for the workspace where they are installed.

[sandy081]

Also, always when extensions are installed, they are enabled globally, never they are enabled for the workspace where they are installed.

So you mean when recommendations are installed, enable only for this workspace automatically?

[n3rd4i]

[...] when recommendations are installed, enable only for this workspace automatically?

That sounds very helpful, I would suggest that, on top of the other points I made earlier.

Additionally, maybe also allowing to disable recommended extensions could prove useful to still keep the global enabled ones untouched.

[whut]

@sandy081

So you mean when recommendations are installed, enable only for this workspace automatically?

Yes! With that single thing it would be easy to maintain different sets of extensions per workspace and keep them in source control.

Here is the workflow:

1. First user disable all extensions except selected few that are used always. This is a required step to use this workflow - this should be documented on Recommended Extensions section in Extensions user guide to make users familiar with this approach.

2. When opening some workspace with recommended extensions that I have already installed, Code automatically enables recommended extensions for current workspace. I believe this should win even over manually "disabled per workspace" extension, as the same behavior is with settings: workspace settings win over user settings. Note that there is no disabling extensions automatically (that kind of idea is proposed in Feature Request: Enable/disable extensions from config file #40239 and Persisting "disable by workspace" settings in source control #18386, IMO it would be irritating, similar is in Ability to enable only [all] recommended extensions #61723 - again this would mean that I am not able to have additional extensions enabled per workspace) nor automatic install, user is still in control here.

3. When opening some workspace with recommended extensions and I do not have them already installed, Code prompts to install them, and with Default extensions scope #51658 I am able to right on the spot enable them only in current workspace. Even without Default extensions scope #51658 it is OK, I just install them, and disable, then reload window to trigger behavior from above point.

In the end we have system that is simple, automatic, source controlled so sharable with the team and still keeps user in control on which extension are installed, and allows to have additional extensions enabled.

I believe it would also solve #57548.

[ArulDhandapani]

Reading all the thread related with this topic, i assume everyone looking similar to below feature what I described with example.

This has to go to ".code-workspace" config file to enable other users as zero config/setup effort in a project, they just open and start coding.

Example File: project.code-workspace

	{
		"folders": [
			{
				"path": "."
			}
		],
		"settings.user": "false",  _<-Enable/Disable user settings located under 'AppData\Roaming\Code\User\settings.json' in a system_
		"settings.folder": "false",  _<-Enable/Disable folder settings located under '.vscode\settings.json' in a project_
		"extensions": {  _<-Extension config_
			"installed": "false",  _<-Enable/Disable user installed extension in their system_
			"[load]": {  _<-Re-load VSCode when "open workspace"_
				"required": [  _<-Listed below extension auto-install if user doesn't have in their system without prompt_
					"ms-python.python",
					"sonarsource.sonarlint-vscode",
					"eamodio.gitlens"
				],
				"optional": [  _<-Listed below extension prompt to user to install, if user doesn't have in their system_
					"euskadi31.json-pretty-printer",
					"silverbulleters.sonarqube-inject"
				],
			},
		}
	}

[jd-solanki]

I am also waiting for this feature.

Here's my workflow: #128030

Additionally, If I create a new project for let's say reproducing some issue I want syntax highlighting for that workspace only and want to enable extensions for that workspace only rather than enabling globally. Enabling them one by one by click on the Gear icon is not I want.

[jd-solanki]

Any updates?

[Junkher]

Any updates?

[ImaniAN]

The way I need this feature right now ...

Sometimes when you working in different workspaces that have code that uses different languages, Frameworks, Platforms or Libraries(the VS Code workspaces)...

You have to enable and disable extensions according to that specific workspace.

Would be pretty cool if when you open a workspace, you are asked if you want to:

firstly: install all recommended workspace extensions
Secondly: Disable all extensions not in the recommended workspace extensions array/list
Lastly: Enable the recommended workspace extensions

SIDE NOTE:

users should be allowed to create a list of "globally available extensions":
def: A list of installed extensions that can be enabled one after another

Use Case (Personal):
Regardless of workspace, repo, language, Framework, Platform or Library or code base if I am using VS Code, I have Kite AutoComplete AI Code and TODO Highlight enabled, because in my opinion I will always need them regardless of what I am working on.

Even if I disable all extensions, it would be helpful to enable extensions that, regardless of the recommended workspace extensions can be enabled as a collective (i.e/ AKA => "globally available extensions")

[av-2024]

Hello?

[VSCodeTriageBot]

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!

[jd-solanki]

This is useful if someone is working with multiple languages. I don't want to use python extension in TS code and vice versa.

To prevent unwanted use of resources we disable the extensions and we don't have an easy way to enable them back on language-specific projects.

[sandy081]

For language specific projects, please check out this feature - #116740