Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Production-ready support of VS Code as a Che editor #20500

Closed
20 of 25 tasks
l0rd opened this issue Sep 21, 2021 · 8 comments
Closed
20 of 25 tasks

Production-ready support of VS Code as a Che editor #20500

l0rd opened this issue Sep 21, 2021 · 8 comments
Labels
area/editor/vscode Issues related to the Code OSS editor of Che area/editors area/plugins kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. roadmap/6-months Epics that are planned to complete in the medium term (within 6 months)

Comments

@l0rd
Copy link
Contributor

l0rd commented Sep 21, 2021

Is your enhancement related to a problem? Please describe

Running VS Code as editor in Che workspaces

Describe the solution you'd like

Additional context

Downstream:

Describe alternatives you've considered

Issues removed from this epic

@l0rd l0rd added kind/enhancement A feature request - must adhere to the feature request template. kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. labels Sep 21, 2021
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 21, 2021
@l0rd l0rd added area/dashboard area/editors area/plugins and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Sep 21, 2021
@nickboldt nickboldt changed the title Adding VS Code as a Che editor Add VS Code as a Che editor Sep 21, 2021
@nickboldt

This comment has been minimized.

@l0rd l0rd changed the title Add VS Code as a Che editor Production-ready support of VS Code as a Che editor Oct 4, 2021
@l0rd l0rd added the roadmap/3-months Epics that are planned to complete in the short term (within 3 months) label Oct 4, 2021
@l0rd l0rd added roadmap/6-months Epics that are planned to complete in the medium term (within 6 months) and removed roadmap/3-months Epics that are planned to complete in the short term (within 3 months) labels Oct 5, 2021
@azatsarynnyy azatsarynnyy added the area/editor/vscode Issues related to the Code OSS editor of Che label Oct 6, 2021
@benoitf
Copy link
Contributor

benoitf commented Oct 12, 2021

cc @sleshchenko if you can include in your next sprint
devfile/devworkspace-operator#628
devfile/devworkspace-operator#629

as it's blocking introduction of this editor in the plug-in registry.

@trust-freedom
Copy link

  • Using OpenVSX instead of MS marketplace.
  • Use the plugin registry as an alternative to OpenVSX.

So in the future, can I directly use OpenVSX marketplace to install extensions in the "Production-ready support of VS Code"? Or must che plugin mode be used?

@benoitf
Copy link
Contributor

benoitf commented Dec 8, 2021

hello @trust-freedom

There are multiple ways so maybe you can express your wishes.

Using OpenVSX directly won't work for airgap mode so we would still need the registry to embed vsix (as of today with offline image of plug-in registry). Also sometimes we may want to add some pre-defined properties

But, plug-in registry could work as a proxy to open-vsx.org (or another in-house instance) or plug-in registry could sync from a predefined/configurable list of extensions or also users could directly use a different registry (like open-vsx.org)

@benoitf benoitf removed the kind/enhancement A feature request - must adhere to the feature request template. label Jan 7, 2022
@azatsarynnyy
Copy link
Member

@azatsarynnyy
Copy link
Member

@azatsarynnyy
Copy link
Member

I've removed #21080 from the sub-task list, as it's not relevant anymore.

nickboldt added a commit to eclipse-che/che-server that referenced this issue Nov 28, 2022
…3099, CRW-3420, eclipse-che/che#20500)

Change-Id: Ib576241488e9ada5465dd45a9bc140cd6b4ed7e6
Signed-off-by: Nick Boldt <nboldt@redhat.com>
nickboldt added a commit to eclipse-che/che-server that referenced this issue Nov 28, 2022
…3099, CRW-3420, eclipse-che/che#20500)

Change-Id: Ib576241488e9ada5465dd45a9bc140cd6b4ed7e6
Signed-off-by: Nick Boldt <nboldt@redhat.com>
@che-bot
Copy link
Contributor

che-bot commented May 27, 2023

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.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 27, 2023
@che-bot che-bot closed this as completed Jun 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/editor/vscode Issues related to the Code OSS editor of Che area/editors area/plugins kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. roadmap/6-months Epics that are planned to complete in the medium term (within 6 months)
Projects
None yet
Development

No branches or pull requests

7 participants