Ability to use and override default profile settings in a custom profile #188612

sandy081 · 2023-07-23T14:46:11Z

Ability to use and override default profile settings in a custom profile

NOTE: Please mention your use case / scenario (NOT how you want to use) for this requirement. Also try if available Profiles features including #156144 are helping

tanishqmanuja · 2023-07-25T04:35:44Z

Use case: #156144 (comment)

tanishqmanuja · 2023-09-07T10:13:03Z

I have recently updated my approach towards maintaining my vscode settings.
Purpose of sharing it here is:

Feedback for improving/ Discussing any alternative method
Reporting the pain points in this approach to vscode devs

EDIT: In C/C++ extensions block, I meant C/C++ specific extensions instead of JS.
LINK: tldraw

Pain Points

These are marked with red arrow

Have to copy all defaults manually
No way of enabling extensions for workspace via code/json. Code can be copy-pasted/automated but not GUI actions.

cdce8p · 2023-09-07T12:15:05Z

No way of enabling extensions for workspace via code/json. Code can be copy-pasted/automated but not GUI actions.

Would love to do that as well. I frequently need to enable the same extensions for new (temporary) workspaces.
In theory it would be possible to edit the state.vscdb database files and overwrite extensionsIdentifiers/enabled but that's something which should be simpler to accomplish.

jcrben · 2023-09-11T19:53:41Z

The use case I envision is for team sharing of settings. I want to create base default settings for all my team members which they can easily override if they feel so inclined. Then I want them to be able to use a profile as well on top of this foundation. If I could do that via something like https://learn.microsoft.com/en-us/windows/terminal/json-fragment-extensions that could be nice altho maybe that's overcomplicating it - I just want a single base.

thernstig · 2023-10-24T08:55:24Z

I believe the solution should be akin ESLint extends, or Ruff extends, or any other similar tool.

The current way of using workbench.settings.applyToAllProfiles is not sufficient to capture everything. Here is an example of this shortcoming. Imagine I have this in the applications setting (Default Profile):

{
  "workbench.settings.applyToAllProfiles": [
    "editor.codeActionsOnSave"
  ],
  "editor.codeActionsOnSave": {
    "source.organizeImports": "never"
  }
}

Imagine I have this in a Web Profile setting.json:

{
  "editor.codeActionsOnSave": {
    "source.organizeImports": "always",
    "source.fixAll.eslint": "always",
    "source.fixAll.markdownlint": "always",
    "source.fixAll.stylelint": "always"
  }
}

There is no way for me to override the individual items in the object.

Setting values can be of various types. Such merging is well handled by normal settings.json merging between user, remote, workspace settings etc, see https://code.visualstudio.com/docs/getstarted/settings#_settings-precedence.

Here is an idea of a better solution:

Default Profile

  "editor.codeActionsOnSave": {
    "source.organizeImports": "never"
  }
}

Web Profile

{
  "extends": ["Default Profile"],
  "editor.codeActionsOnSave": {
    "source.organizeImports": "always",
    "source.fixAll.eslint": "always",
    "source.fixAll.markdownlint": "always",
    "source.fixAll.stylelint": "always"
  }
}

This has several benefits:

You can nest multiple extends where precedence is from right-to-left (i.e. last item has highest precedence). This enables a hierarchy of profiles e.g. "default -> web -> web with Golang backend" OR "default -> web -> web with Python backend".
You easily see in the lower-layer profiles what they extend, instead of having to go to the Default Profile to see what gets into lower profiles.
https://code.visualstudio.com/docs/getstarted/settings#_settings-precedence can be respected with type merging, meaning objects merge better.

If doing this, it would be great if a rename of a profile name also updates extends: ["Default Profile"], so the names sync, which could easily be missed otherwise.

thernstig · 2023-10-26T14:43:53Z

Thinking more about #188612 (comment), it might even be more beneficial to create this extends functionality directly built into the Profiles. Rationale being that then also Extensions, Keyboard Shortcuts etc. could be merged in a nicer way.

So let's say you have Default -> Python Development -> Python Development Ruff Default -> Python Development -> Python Development Flake8, you could share the Python Development and get the Python extension in both, but different linter extensions Ruff vs. Flake8. Just as a dumb example. So not only settings would be merged, but also the others. So Extensions would be a be a union of the all extended Profiles.

sharpchen · 2023-11-15T07:06:06Z

I wonder with current solution, when create new profile from default with settings, does it simply copy settings or references them from default?

brettcannon · 2023-11-15T19:30:50Z

I wonder with current solution, when create new profile from default with settings, does it simply copy settings or references them from default?

I believe it references them.

soimon · 2023-11-16T22:44:54Z

I wholeheartedly agree with @thernstig on #188612 (comment): this is the way I would expect the system to work, given my experience with various configuration files that follow the same logic.

I would like to propose the idea of multiple inheritance (with the settings being merged in order, i.e., the latter one overwriting the earlier one). This would allow you to truly separate different contexts and environments.

You could have profiles for each language and context, stacking them just like you stack your tech stack:

{
  extends: ["Svelte Profile", "Python Profile"]
  // Svelte frontend with Python backend specific settings here
}

graph TD;
    golang(Golang)
    svelte(Svelte)
    python(Python)
    edu("Presentation (larger fonts, etc.)")
    svelte & golang-->c1[Svelte frontend with Golang backend]
    svelte & python-->c2[Svelte frontend with Python backend]

In this approach, a profile becomes an expression of extensions and settings you'd like to have available when working in a specific context or using a particular technology. It's like knowing you're heading to the gym and doing groceries afterward: you simply grab your sports bag and wallet, and the union of these allows you to do all your activities without having to think too much about what's inside either of them.

To avoid having to set up a jungle of profile combinations, it makes sense to specify this union in your workspace file, as the combinationary aspect is typically specific to the workspace.

While this idea might extend beyond the initial scope of what this system was intended for, I think it offers the most flexible and (for a lot of developers) familiar approach.

thernstig · 2023-11-17T10:03:03Z

@soimon yes, multiple inheritance is captured in #188612 (comment) since the example uses an array for extending.

However, I think I make a fair point in #188612 (comment) that this should possibly not go into the settings.json but rather Profiles directly.

tanishqmanuja · 2024-01-31T10:43:57Z

Since, this feature is still not supported. I am using the extension enable/disable method, can anyone tell me how to suppress these warning when the extensions are disabled.

jmevel · 2024-02-05T08:07:20Z

@tanishqmanuja when you switch to a profile you have to reopen the settings file because VS Code will keep the previous settings file open.

I always add a comment at the top of all my settings file to quickly know which one I'm currently modifying.
For example I have // DEFAULT settings for the default profile and // RUST profile settings for my Rust one.

The default' settings file is located under (for Windows) under %APPDATA%\Roaming\Code\User but any other profile's settings file will be under %APPDATA%\Roaming\Code\User\profiles\profile_ID

Your setting won't be recognized if you don't have this specific extension enabled in the current profile you selected.

tanishqmanuja · 2024-02-05T20:43:49Z

@jmevel, Actually I dont want to switch profile at all here ( bc state of profiles is currently a mess ofc ). What I am doing is making my default profile installing all essential extensions and then disabling them as soon as they are installed. I only enable the required extension for the workspace, for example rust analyzer for rust workspace.

thernstig · 2024-02-06T08:18:06Z

@jmevel, Actually I dont want to switch profile at all here ( bc state of profiles is currently a mess ofc ). What I am doing is making my default profile installing all essential extensions and then disabling them as soon as they are installed. I only enable the required extension for the workspace, for example rust analyzer for rust workspace.

The current solution is not in the best shape, as key aspects like overriding and sync between machines seem to not behave in a great way, but let's stay positive it changes in the future with our feedback :)

I made a smaller summary here of some problems: #196718 (comment)

jmevel · 2024-02-16T10:26:08Z

@jmevel, Actually I dont want to switch profile at all here ( bc state of profiles is currently a mess ofc ). What I am doing is making my default profile installing all essential extensions and then disabling them as soon as they are installed. I only enable the required extension for the workspace, for example rust analyzer for rust workspace.

Oh I see, that's a smart workaround, I didn't even think of it 😅

mschwandt98 · 2024-04-10T05:38:28Z

Hi! 😊 What is the status of this feature? Has a decision already been made? If not, what exactly is missing for a decision? Many of my colleagues and I would be very happy if this feature would be implemented in VSCode.

PierreLouisPAUGAM · 2024-06-27T09:12:25Z

Hi @sandy081 😊
I wonder if this feature is still being worked on or if it is currently stalled.
Would you mind giving us an update ?

gjsjohnmurray · 2024-06-27T11:04:02Z

@PierreLouisPAUGAM FYI the team is focused on endgame this week and next week.

sandy081 · 2024-06-28T08:12:43Z

This is not in our plan yet.

dallenbaldwin · 2024-09-12T04:27:01Z

I found myself here after looking for a way for my profiles to inherit from a default profile. I hate having to constantly remember that some new extension I found in one profile now has to be installed in all my other profiles, and then I have to switch profiles to keep it up to date.

A pretty common use case, I would argue, is markdown. Most people have to write markdown regardless of which language or development environment they work with. There are a lot of really good markdown extensions out there for mermaid, automatic link tables of contents, printing as PDF, etc.

Another would be GitLens. It adds many features to the Source Control panel that are applicable regardless of language, dev tools, etc.

It would make sense to have a base profile hold GitLens and all the markdown extensions I like, and then, as others have mentioned, add/remove based on the framework, development environment, language, etc.

gjsjohnmurray · 2024-09-12T04:46:06Z

@dallenbaldwin are you aware that extensions can optionally be installed for all profiles?

https://code.visualstudio.com/docs/editor/profiles#_apply-an-extension-to-all-profiles

dallenbaldwin · 2024-09-12T04:56:58Z

Ah! I've never noticed that before! Thank you 😁

Does it also apply that extension to new profiles or is it only another way to copy the extension to all current profiles?

gjsjohnmurray · 2024-09-12T06:46:30Z

Does it also apply that extension to new profiles

This should be easy enough to check. Also relevant is #193446 which is milestoned for the current iteration.

gjsjohnmurray · 2024-09-12T06:47:16Z

Does it also apply that extension to new profiles

This should be easy enough to check. Also relevant is #193446 which is milestoned for the current iteration.

CTNOriginals · 2024-10-30T21:06:46Z

I have been looking for a feature like this for a while now. The way I would apply this feature is that I would create some sort of "base" profile that all profiles will inherit from so it can then serve as a sort of essentials bundle that i would apply to all profiles no matter what the profile is created and used for. This would make it a lot easier if i would find a new extension that has to be set up in a specific way so I don't have to copy paste those settings across all profiles. This would also apply to keybinds and other profile related settings.

sanmai-NL · 2024-11-20T11:56:53Z

I found myself here after looking for a way for my profiles to inherit from a default profile. I hate having to constantly remember that some new extension I found in one profile now has to be installed in all my other profiles, and then I have to switch profiles to keep it up to date.

A pretty common use case, I would argue, is markdown. Most people have to write markdown regardless of which language or development environment they work with. There are a lot of really good markdown extensions out there for mermaid, automatic link tables of contents, printing as PDF, etc.

Another would be GitLens. It adds many features to the Source Control panel that are applicable regardless of language, dev tools, etc.

It would make sense to have a base profile hold GitLens and all the markdown extensions I like, and then, as others have mentioned, add/remove based on the framework, development environment, language, etc.

@dallenbaldwin
See:

sandy081 added under-discussion Issue is under discussion for relevance, priority, approach user-profiles User profile management labels Jul 23, 2023

sandy081 self-assigned this Jul 23, 2023

This was referenced Jul 25, 2023

Profiles: Extend from Default Profile #156144

Closed

Test Partial Profiles #188613

Closed

This was referenced Aug 29, 2023

Profiles Inheritance #191516

Closed

Support Profile Inheritance #191224

Closed

thernstig mentioned this issue Oct 24, 2023

"Apply Extension to all Profiles" does not work when selected in the "LOCAL - INSTALLED" window in case the extensions are installed in the remote extension host #196351

Closed

thernstig mentioned this issue Jan 31, 2024

Improvement: Applying an extension to all Profiles does not sync properly between machines #196718

Closed

sliedes mentioned this issue Jul 2, 2024

UI: Make workspace/foldings settings reflect more clearly true/false/unchanged #219676

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Ability to use and override default profile settings in a custom profile #188612

Ability to use and override default profile settings in a custom profile #188612

sandy081 commented Jul 23, 2023 •

edited

Loading

tanishqmanuja commented Jul 25, 2023

tanishqmanuja commented Sep 7, 2023 •

edited

Loading

cdce8p commented Sep 7, 2023

jcrben commented Sep 11, 2023 •

edited

Loading

thernstig commented Oct 24, 2023 •

edited

Loading

thernstig commented Oct 26, 2023 •

edited

Loading

sharpchen commented Nov 15, 2023

brettcannon commented Nov 15, 2023

soimon commented Nov 16, 2023 •

edited

Loading

thernstig commented Nov 17, 2023

tanishqmanuja commented Jan 31, 2024

jmevel commented Feb 5, 2024 •

edited

Loading

tanishqmanuja commented Feb 5, 2024

thernstig commented Feb 6, 2024

jmevel commented Feb 16, 2024

mschwandt98 commented Apr 10, 2024

PierreLouisPAUGAM commented Jun 27, 2024 •

edited

Loading

gjsjohnmurray commented Jun 27, 2024

sandy081 commented Jun 28, 2024

dallenbaldwin commented Sep 12, 2024

gjsjohnmurray commented Sep 12, 2024

dallenbaldwin commented Sep 12, 2024

gjsjohnmurray commented Sep 12, 2024

gjsjohnmurray commented Sep 12, 2024

CTNOriginals commented Oct 30, 2024

sanmai-NL commented Nov 20, 2024

Ability to use and override default profile settings in a custom profile #188612

Ability to use and override default profile settings in a custom profile #188612

Comments

sandy081 commented Jul 23, 2023 • edited Loading

tanishqmanuja commented Jul 25, 2023

tanishqmanuja commented Sep 7, 2023 • edited Loading

Pain Points

cdce8p commented Sep 7, 2023

jcrben commented Sep 11, 2023 • edited Loading

thernstig commented Oct 24, 2023 • edited Loading

thernstig commented Oct 26, 2023 • edited Loading

sharpchen commented Nov 15, 2023

brettcannon commented Nov 15, 2023

soimon commented Nov 16, 2023 • edited Loading

thernstig commented Nov 17, 2023

tanishqmanuja commented Jan 31, 2024

jmevel commented Feb 5, 2024 • edited Loading

tanishqmanuja commented Feb 5, 2024

thernstig commented Feb 6, 2024

jmevel commented Feb 16, 2024

mschwandt98 commented Apr 10, 2024

PierreLouisPAUGAM commented Jun 27, 2024 • edited Loading

gjsjohnmurray commented Jun 27, 2024

sandy081 commented Jun 28, 2024

dallenbaldwin commented Sep 12, 2024

gjsjohnmurray commented Sep 12, 2024

dallenbaldwin commented Sep 12, 2024

gjsjohnmurray commented Sep 12, 2024

gjsjohnmurray commented Sep 12, 2024

CTNOriginals commented Oct 30, 2024

sanmai-NL commented Nov 20, 2024

sandy081 commented Jul 23, 2023 •

edited

Loading

tanishqmanuja commented Sep 7, 2023 •

edited

Loading

jcrben commented Sep 11, 2023 •

edited

Loading

thernstig commented Oct 24, 2023 •

edited

Loading

thernstig commented Oct 26, 2023 •

edited

Loading

soimon commented Nov 16, 2023 •

edited

Loading

jmevel commented Feb 5, 2024 •

edited

Loading

PierreLouisPAUGAM commented Jun 27, 2024 •

edited

Loading