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.

Sign up for GitHub

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

Jump to bottom

Document how to analyse Theia support for a given VS Code extension #13849

Closed
l0rd opened this issue Jul 15, 2019 · 3 comments
Closed

Document how to analyse Theia support for a given VS Code extension #13849

l0rd opened this issue Jul 15, 2019 · 3 comments
Labels
area/doc Issues related to documentation kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.
Milestone
7.x (Later, Futur...

Comments

@l0rd
Copy link
Contributor

l0rd commented Jul 15, 2019 •
edited
Loading

We are currently tracking VS Code and Theia compability with regards to the support of the VS Code extension APIs.

It would be nice to help users to understand if a VS Code extension is expected to run properly in Theia (because the API it calls are already implemented in Theia) or if, in the contrary it may behave incorrectly (because some API are not or partially implemented).

These manual steps could be added in che-docs, in section "Using a Visual Studio Code extension in Che".
@l0rd l0rd added kind/enhancement A feature request - must adhere to the feature request template. team/ide2 area/doc Issues related to documentation labels Jul 15, 2019
@nickboldt
Copy link
Contributor

I'm guessing this isn't urgent for 7.0 or 7.1, but might be nice for 7.2?

@nickboldt nickboldt added this to the 7.x milestone Jul 15, 2019
@nickboldt nickboldt added the status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. label Jul 15, 2019
@tsmaeder
Copy link
Contributor

This issue should be on the theia repo, not here.

@che-bot
Copy link
Contributor

che-bot commented Mar 11, 2020

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 Mar 11, 2020
@che-bot che-bot closed this as completed Mar 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/doc Issues related to documentation kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.
Projects
None yet
Milestone
7.x (Later, Future, Never)
Development

No branches or pull requests
4 participants
@nickboldt @l0rd @tsmaeder @che-bot