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

Feature: Support Create Settings Profile For Current Workspace #164251

Closed
joyceerhl opened this issue Oct 21, 2022 · 4 comments
Closed

Feature: Support Create Settings Profile For Current Workspace #164251

joyceerhl opened this issue Oct 21, 2022 · 4 comments
Assignees
Labels
feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code user-profiles User profile management
Milestone

Comments

@joyceerhl
Copy link
Contributor

This milestone I've done investigation on * activated extensions and am motivated to find ways to reduce their impact on perceived VS Code performance. One way to frame the problem is that if I am a user who has installed an extension which is either * activated or later becomes * activated, I pay the cost of that extension activating (code loading plus running whatever is in its activate method) whenever VS Code starts up. This also applies to extensions which are onStartupFinished activated or otherwise eagerly activated.

I wonder whether there is an opportunity to make it easier for users to manage such extensions and therefore extract better performance out of VS Code (e.g. I audited my installed extensions list and immediately saw improved startup times).

  • For example, today we have the ability to disable extensions for a specific workspace. We now have the dropdown button to Install and Install pre-release for extensions. I wonder if we could have an additional action to install extensions only for a specific workspace. In the same way that we show the option to install pre-releases first in Insiders, we could show the option to install and enable (workspace) first for eagerly activated extensions
  • This potentially relates to settings profiles which controls which extensions are installed/enabled. Perhaps we could have a command like Extensions: Create Settings Profile For Current Workspace which takes the user through creating an optimized settings profile with just the extensions that need to be installed and activated. One qualm I have with the Settings Profiles: Create From Current Settings Profile... command is that it doesn't let me review what's in the profile before creating. For the extensions-oriented action, we could have a quickpick with checkboxes for which extensions are going to be included in the profile (and maybe deselect the extensions which are installed but haven't been activated for the current workspace). This could also be an opportunity to include extensions that are recommended for the current workspace via .vscode/extensions.json.
@sandy081
Copy link
Member

@joyceerhl Good ideas and the first idea is already requested. Extensions: Create Settings Profile For Current Workspace seems to be an interesting thought. It was not clear to me what is the clear action item here and how the settings profile action will be helping.

@sandy081 sandy081 added the info-needed Issue requires more information from poster label Oct 26, 2022
@joyceerhl
Copy link
Contributor Author

We can consider this issue a feature request for Create Settings Profile For Current Workspace then :)

@sandy081 sandy081 changed the title Make it easier to enable just the extensions I want for a given repository/workspace Feature: Support Create Settings Profile For Current Workspace Oct 28, 2022
@sandy081 sandy081 added feature-request Request for new features or functionality user-profiles User profile management labels Oct 28, 2022
@sandy081 sandy081 added this to the Backlog milestone Oct 28, 2022
@vscodenpa
Copy link

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

@vscodenpa vscodenpa closed this as not planned Won't fix, can't repro, duplicate, stale Nov 4, 2022
@sandy081 sandy081 removed the info-needed Issue requires more information from poster label Nov 4, 2022
@sandy081 sandy081 reopened this Nov 4, 2022
@sandy081
Copy link
Member

Profiles feature is still in preview mode and we do not know whether this will be a feature which users want or not. Hence I am closing this for now and reopen this when more users wanted this.

@sandy081 sandy081 added the *out-of-scope Posted issue is not in scope of VS Code label Dec 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code user-profiles User profile management
Projects
None yet
Development

No branches or pull requests

3 participants