Skip to content

Identify design inconsistencies with UI + JSON expriences #84309

@miguelsolorio

Description

@miguelsolorio

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
  • Keybindings
  • Snippets
  • Extensions

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
    • editor.rulers
  • Boolean or Strings
    • editor.fontLigatures
  • Inputs
    • terminal.integrated.automationShell.linux
    • terminal.integrated.automationShell.osx
    • terminal.integrated.automationShell.windows
  • Deprecated settings

image

JSON

image

Keybindings

UI

  • IntelliSense for when clause
  • Sorting columns
  • Reset keys recorder

image

JSON

image

Snippets

UI

  • Configuring snippets

image

JSON

  • Central management of all snippets

image

Extensions

UI

  • Bulk install/uninstall

image

CLI

code --install-extension ms-azuretools.vscode-azurefunctions

JSON

  • No experience

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.

Metadata

Metadata

Assignees

Labels

debtCode quality issuesuxUser experience issues

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions