Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-3586

Auto-install VS Code extensions specified in `.vscode/extensions.json`

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 3.4.0.GA
    • 3.4.0.GA
    • docs
    • False
    • None
    • False
    • Hide
      = Automatic installation of recommended extensions

      With this update, the recommended extensions from the `.vscode/extensions.json` file are automatically installed at workspace startup.
      Show
      = Automatic installation of recommended extensions With this update, the recommended extensions from the `.vscode/extensions.json` file are automatically installed at workspace startup.
    • Enhancement
    • Done

    Description

      Synced from Eclipse Che issue

      https://github.com/eclipse/che/issues/21701

      Is your enhancement related to a problem? Please describe

      VS Code allows providing the extensions list (.vscode/extensions.json) that will be recommended for installation. The user needs to confirm that she really wants to install the recommended extensions set once VS Code starts (docs link).

      While it looks great when running VS Code as a desktop application (Electron), it looks more like a redundant step when using VS Code in the cloud context.

      Considering that one of the main goals of Che is to provide a fully ready environment for the developers, we can automate the step when the user needs to confirm what is already declared in the project's config file. Not to bother the user by accepting pop-ups. Note, that in some cases there might be a few suggestions to install the extensions.

      Everything described above might not be a big problem for the experienced VS Code user. But we see from the internal feedback that it is a problem for those who have no previous experience with VS Code. For people, it's not obvious why the extensions declared in the .vscode/extensions.json config file are not actually installed in the running VS Code OOTB. Also, it turned out that for some users the relatively tiny notification in the window corner does not attract much attention:

      Describe the solution you'd like

      With the VS Code CLI, it's possible to install the extensions set forcibly, without the user's confirmation (docs link).

      One of the options: the user can provide a dedicated attribute in the Devfile to tell VS Code that the recommended extensions, provided in the .vscode/extensions.json, are actually mandatory and must be installed without the user's confirmation.

      Release Notes Text

      Recommended extensions in file .vscode/extensions.json are automatically installed by che-code at workspace startup. Before the developer get prompted to install them. This is the behavior we had in che-theia as well.

      Attachments

        Activity

          People

            rhn-ecs-pkovar Petr Kovar (Inactive)
            jiralint.codeready Bot Codeready
            Jana Vrbkova Jana Vrbkova
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: