4 ms·
One user programmatically changing things to suit themselves is supposed to do so in their user settings, which has precedence over the checked-in copy. That wa
by Hackbraten 4y ago
One user programmatically changing things to suit themselves is supposed to do so in their user settings, which has precedence over the checked-in copy. That way, you have the best of both worlds: easy set-up for everyone who wants it but you can override it without touching the VCS.
- Hackbraten 4y agoUpdate: turns out the precedence rules are a little more subtle than I thought. See also: https://code.visualstudio.com/docs/getstarted/settings#_settings-precedence https://code.visualstudio.com/docs/getstarted/settings#_sett...
- DangitBobby 4y agoCan you override user settings at the project level?
- Hackbraten 4y agoYes, project-level (aka workspace) settings generally override user settings. But then again, language-specific settings will trump all other settings. And that’s one way to override workspace-level settings in your user settings if you want. Here’s a detailed list of all levels of settings in VS Code, ordered by precedence: https://code.visualstudio.com/docs/getstarted/settings#_settings-precedence https://code.visualstudio.com/docs/getstarted/settings#_sett...