Che commands should be of type task or launch
See original GitHub issueDescription
VS Code (and thus Theia) does a clear distinction between a task (linting, building, packaging, testing or deploying) and a launch configuration (run, debug an application).
Currently all Che commands are translated into Theia tasks. As a consequence the UX is bad for run/debug commands. For example, when a user defines a debug command (in a devfile
or from the Che dashboard), he won’t be able to run it from Theia Debug menu.
This issue is about adding an attribute (or a label or an annotation) to the current Che command model (in a workspace config and in a devfile) so that a user will be able to specify if the command should be translated into a task or a launch config.
N.B. This issue is part of epic #12709 and is not about changing the mechanism that translates Che commands into Theia tasks or launch (there is #12711 for that).
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (11 by maintainers)
Top GitHub Comments
vscode has 'group’s for tasks. I do not think this is supported on theia but it should be. groups allows vscode to identify a task as build or test. I think we should consider such a classification for commands on devfile as well.
Issues go stale after
180
days of inactivity.lifecycle/stale
issues rot after an additional7
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.