User settings don't get overridden by workspace settings when default value is used

[SetTrend]

Issue Type: Bug

After having changed a setting's value in user settings, it's not possible to override the changed value with the default VS Code value in workspace settings:

Current Behaviour

VS Code doesn't set overrides for default values.

Desired Behaviour

User settings differ from user to user, whereas workspace settings don't.

Adding a workspace setting tells the team that a particular setting is mandatory for the project, no matter what the actual user settings are.

So any workspace setting that's in the workspace settings settings.json file must not be automatically removed. Only when removing is explicitly desired.

Hence ...

1. Setting any value in the Workspace Settings editor should - regardless of the actual value - always be added to the corresponding workspace settings settings.json file.

2. I suggest to add a Remove button to each setting in Workspace Settings editor that's only visible next to each setting that's present in the corresponding settings.json file in the Workspace Settings editor. Clicking that button should remove that setting from the workspace settings settings.json file.

---

VS Code version: Code 1.30.0 (c6e592b, 2018-12-11T22:29:11.253Z)
OS version: Windows_NT x64 10.0.17134

Extensions (8)

Extension	Author (truncated)	Version
vscode-twig-pack	baj	1.0.0
gitlab-workflow	fat	1.5.1
vscode-firefox-debug	hbe	1.6.0
vscode-language-pack-de	MS-	1.27.2
Go	ms-	0.7.0
PowerShell	ms-	1.10.1
debugger-for-chrome	msj	4.11.1
markdown-all-in-one	yzh	1.8.0

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• Workspace settings should use User setting as default setting (#58927)
• New settings editor: workspace does not inherit settings (#55203)
• new settings editor should not automatically remove a setting from the json when it is set to any value explicitly (#58901)
• Workspace setting default value in new Setting Editor is ambiguous (#50827)
• Boolean settings can't be un-set at workspace level using new settings editor if set at user level (#58791)

[SetTrend]

Closed as duplicate of #58038.