The eslint.nodePath value in .vscode/settings.json does not get updated

[trevor-bliss]

Summary

The eslint.nodePath value in .vscode/settings.json does not get updated with the highest local version of eslint-tool. This is for core workspaces in ui-foo-components projects.

Most likely this is because the merging logic of the settings.json intentionally does not override existing values.

Steps To Reproduce:

1. Do a full core build.
2. Run the ESLint corecli command.
3. Load VS Code with the root of the project at a specific project (e.g., ui-force-components).
4. Check the value of eslint.nodePath.

Expected result

The eslint.nodePath value should point to the highest local version of eslint-tool on my local machine.

Actual result

The eslint.nodePath is never updated once initially set.

Additional information

VS Code Version: 1.57.1

SFDX CLI Version:

OS and version: Mac 10.14.6

[xyc]

We should probably allow overwriting at least the key eslint.nodePath. Workaround for this is: set eslint.nodePath in .vscode/settings.json manually to the path to the highest version in ~/tools/eslint-tools, or delete the eslint.nodePath entry and it will get reset.