Document the Che-specific features we've added to Che's VS Code editor

[azatsarynnyy]

Is your task related to a problem? Please describe

In the Che-Code project, we extended the vanilla VS Code with the Che-specific features and made some adaptations of VS Code's internals to the Che environment.

While it does everything the user might expect from VS Code running in Che, there's no way to read the details of using the particular feature and learn about some important aspects of its behavior.

Describe the solution you'd like

We need to document all the Che-specific features, we've added to our VS Code assembly, on the Che documentation website.

Describe alternatives you've considered

No response

Additional context

Below is the list of the features we can consider to document:

• running the Devfile Commands as VS Code Tasks with the possibility to run them in any container
• opening VS Code terminals to DevWorkspace containers
• detection of the opened ports and suggestions exposing corresponding apps' URLs
• monitoring the system resources of the DevWorkspace containers
• authentication on GitHub
• sending the user's activities to prevent a DevWorkspace from stopping by an idle timeout
• added the helper extension to interact with DevWorkspace. It may be used by the custom extensions which need to work with DevWorkspace directly
• navigating to Che Dashboard from the IDE

Some low-level adaptations to make VS Code work in Che smoothly:

• auto-install the recommended extensions
• idled DevWorkspace detection (in progress)
• the white-labeling capabilities

[l0rd]

added the helper extension to interact with DevWorkspace. It may be used by the custom extensions which need to work with DevWorkspace directly

Is the helper related to the vscode handler? The handler is not required to inject information about the IDE in the tooling container anymore (see container contributions epic) so I am wondering if we can remove it completly from che-code repo (and add a subtask to #21736) or if we still need it.

[azatsarynnyy]

Is the helper related to the vscode handler?

@l0rd it isn't related to a DevWorkspace handler, but it's mostly to simplify fetching some information from a DevWorksapce. Probably, something not worth documenting, as it's more internal stuff.

As for getting rid of the Che-Code DevWorkspace handler, I've just filed

• Remove the DevWorkspace handler code from the Che-Code repository #21837
  and included it in the epic
• [epic] Begin using DevWorkspace Operator container contributions functionality #21736

I believe we do not need a dedicated issue for Che-Theia's DevWorkspace handler, as it will be part of

• Sunset Che Theia as a built-in Che editor #21771

[max-cx]

@azatsarynnyy and @l0rd, how would you compare the expected docs content between the VS Code and the IntelliJ editors (like for any editor Che supports)? I mean should we be expecting a similar issue with a similar scope of documentation for an IntelliJ editor in the future? Or is this docs focus just on VS Code?

[azatsarynnyy]

@max-cx these docs focus just on VS Code

[l0rd]

@max-cx these docs focus just on VS Code

ok, these are just for VS Code. But we have worked on similar features (such as devfile command support) for JetBrains IDE and we should document that.

[azatsarynnyy]

@max-cx these docs focus just on VS Code

ok, these are just for VS Code. But we have worked on similar features (such as devfile command support) for JetBrains IDE and we should document that.

okay, then here's the corresponding issue for the IDEA editor:

• Document the Che-specific features we've added to Che's IDEA editor #21841

[bdwyertech]

Is there still a concept of directly specifying plugins like theia had via .che/che-theia-plugins.yaml attribute? I do not see any of that logic in the devworkspace-handler for che-code.

schemaVersion: 2.1.0
attributes:
  .che/che-theia-plugins.yaml: |
    - repository:
        url: 'https://github.com/chef/vscode-chef'
        revision: 2.1.0
      extension: https://github.com/bdwyertech/vscode-chef/releases/download/che/chef-software.Chef-2.1.0.vsix

[azatsarynnyy]

@bdwyertech you can declare the VS Code extensions in the .vscode/extensions.json file and they will be installed automatically in Che-Code.
E.g.: https://github.com/eclipse-che/che-docs/blob/main/.vscode/extensions.json

[max-cx]

I opened RHDEVDOCS-5026 to assign a technical writer when the developers are ready to start preparing more content on this topic.

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

[azatsarynnyy]

/remove-lifecycle stale

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.