The second line contains the URL of the plugin registry where the editor is published.

The first line specifies the identifier of the editor. che folder and add a che-editor.yaml file with the following content in it: id: che-incubator/che-code/insiders The easiest way to use Visual Studio Code for a given project is to reference it from a che-editor.yaml file in a Git repository.Ĭreate a. Option 1: Adding che-editor.yaml in the Git repository

We'll take a quick look at each approach. We can reference the online Che registry using a file in the Git repository or through a URL parameter. OpenShift Dev Spaces has its own internal plugin registry, but it can use external registries too, including the online Eclipse Che plugin registry. Visual Studio Code is included in the Eclipse Che plugin registry with the identifier che-incubator/che-code/insiders. Select Visual Studio Code as the editor of a Dev Space environment But Eclipse Che, which is the upstream project for OpenShift Dev Spaces, already includes it, and we can easily use it in OpenShift Dev Spaces too. What about Visual Studio Code? Although we plan to use it as the default IDE in future versions of OpenShift Dev Spaces, Visual Studio Code is not included in version 3.0.

Currently, the editors included with OpenShift Dev Spaces are Eclipse Theia and JetBrains IntelliJ IDEA. Version 3.0 has just been released, and it allows you to choose the IDE that will be included in the development environment. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) is an OpenShift-native developer environment server.

Online visual studio code