Normalize open*settings commands args

• VSCode Version: 1.41.1
• OS Version: Win10 1909

Steps to Reproduce:

In an extension:

1. commands.executeCommand(‘workbench.action.openWorkspaceSettings’, ‘telemetry’);
2. Workspace settings open, but without a search filter

No, as there is nothing to run that code

[SpenceV1]

This is exactly what I need to programmatically open the workspace settings for my extension, allowing users to easily make changes. For anyone who needs this feature, execute openSettings with your search, then execute openWorkspaceSettings. It will switch the current settings window over to workspace settings while keeping your search string.

Example vscode.commands.executeCommand('workbench.action.openSettings', 'telemetry' ); vscode.commands.executeCommand('workbench.action.openWorkspaceSettings');

Although this works, I still believe these commands should be consistent. I believe my use case is exactly why we need this, a per project/workspace settings window for extensions at the click of a button rather than multiple quickPicks.

[rainfore]

Same issue. I just want to open the workspace settings and filter by my extension name.