Overview
This issues is to cover the various experiences where we have a rich editing experiences (UI) and a text based configuration (JSON). Some of these experiences have overlap while others have gaps that we'd like to be covered. Below is a list of areas where we have these experience with a list of features that are either missing or need better coverage.
Settings
UI
- Objects
files.associations
emmet.includeLanguages
editor.codeActionsOnSave
editor.quickSuggestions
editor.tokenColorCustomizationsExperimental
terminal.integrated.env.linux
terminal.integrated.env.osx
terminal.integrated.env.windows
remote.extensionKind
sync.ignoredSettings
emmet.syntaxProfiles
emmet.variables
- Nested Objects
editor.tokenColorCustomizations
workbench.colorCustomizations
workbench.experimental.editorAssociations
launch
extensions.confirmedUriHandlerExtensionIds
workbench.experimental.editorAssociations
remote.extensionKind
- Arrays
- Boolean or Strings
- Inputs
terminal.integrated.automationShell.linux
terminal.integrated.automationShell.osx
terminal.integrated.automationShell.windows
- Deprecated settings

JSON

Keybindings
UI
- IntelliSense for
when clause
- Sorting columns
- Reset keys recorder

JSON

Snippets
UI

JSON
- Central management of all snippets

Extensions
UI

CLI
code --install-extension ms-azuretools.vscode-azurefunctions
JSON
devcontainers.json is a configuration file for our remote containers, and in that configuration file you can specify extensions via:
{
"extensions": [
"ms-azuretools.vscode-azurefunctions",
"ms-vscode.csharp"
]
}
We should look at adopting a similar patter for user extensions, in the same way that you can edit user settings via JSON.
Overview
This issues is to cover the various experiences where we have a rich editing experiences (UI) and a text based configuration (JSON). Some of these experiences have overlap while others have gaps that we'd like to be covered. Below is a list of areas where we have these experience with a list of features that are either missing or need better coverage.
Settings
UI
files.associationsemmet.includeLanguageseditor.codeActionsOnSaveeditor.quickSuggestionseditor.tokenColorCustomizationsExperimentalterminal.integrated.env.linuxterminal.integrated.env.osxterminal.integrated.env.windowsremote.extensionKindsync.ignoredSettingsemmet.syntaxProfilesemmet.variableseditor.tokenColorCustomizationsworkbench.colorCustomizationsworkbench.experimental.editorAssociationslaunchextensions.confirmedUriHandlerExtensionIdsworkbench.experimental.editorAssociationsremote.extensionKindeditor.rulerseditor.fontLigaturesterminal.integrated.automationShell.linuxterminal.integrated.automationShell.osxterminal.integrated.automationShell.windowsJSON
Keybindings
UI
whenclauseJSON
Snippets
UI
JSON
Extensions
UI
CLI
code --install-extension ms-azuretools.vscode-azurefunctionsJSON
devcontainers.jsonis a configuration file for our remote containers, and in that configuration file you can specify extensions via:{ "extensions": [ "ms-azuretools.vscode-azurefunctions", "ms-vscode.csharp" ] }We should look at adopting a similar patter for user extensions, in the same way that you can edit user settings via JSON.