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

New projects are lost after a workspace restart

XMLWordPrintable

    • False
    • None
    • False
    • Release Notes
    • Hide
      = New projects lost after a workspace restart

      Before this update, the Microsoft Visual Studio Code - Open Source launcher was adding projects from `devfile.yaml` to `.vscode-workspace` configuration file only during the initial workspace startup.
      If you added a new project (or dependent project) to the devfile and restarted the workspace using the "Restart Workspace from Local Devfile" option, the new project was not added to the configuration file. This resulted in you not seeing the project even though all the projects were cloned in the `/projects` folder. With this release, projects are correctly updated in the `.vscode-workspace` configuration file.
      Show
      = New projects lost after a workspace restart Before this update, the Microsoft Visual Studio Code - Open Source launcher was adding projects from `devfile.yaml` to `.vscode-workspace` configuration file only during the initial workspace startup. If you added a new project (or dependent project) to the devfile and restarted the workspace using the "Restart Workspace from Local Devfile" option, the new project was not added to the configuration file. This resulted in you not seeing the project even though all the projects were cloned in the `/projects` folder. With this release, projects are correctly updated in the `.vscode-workspace` configuration file.
    • Bug Fix
    • Done

      Before this release, VS Code launcher was adding projects from the devfile to .vscode-workspace configuration file only during the initial workspace startup. However, if a new project (or dependent project) was added to the devfile.yaml, and the workspace was restarted using the Restart Workspace from Local Devfile, the new project was not added to the .vscode-workspace configuration file, and the user was not able to see it in the VS Code, although all the projects were cloned in /projects folder. The defect has been fixed in this release and now the projects are correctly updated in the .vscode-workspace configuration file.

            jvrbkova@redhat.com Jana Vrbkova
            jvrbkova@redhat.com Jana Vrbkova
            Maksym Musienko Maksym Musienko
            Jana Vrbkova Jana Vrbkova
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: