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

VS Code side panel for Devfile Commands #21702

Open
azatsarynnyy opened this issue Sep 14, 2022 · 11 comments
Open

VS Code side panel for Devfile Commands #21702

azatsarynnyy opened this issue Sep 14, 2022 · 11 comments
Labels
area/editor/vscode Issues related to the Code OSS editor of Che kind/enhancement A feature request - must adhere to the feature request template. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@azatsarynnyy
Copy link
Member

Is your enhancement related to a problem? Please describe

Currently, the Devfile Commands are translated to VS Code Tasks. A typical way to run such a Task is using the Commands Palette. Although it is the only way provided by VS Code, it's not the best UX. Especially for the users who are not very familiar yet with the VS Code.

Describe the solution you'd like

It would be great to add a side panel with the Devfile Commands listed. It can provide:

  • an easy way to find it in the UI
  • a simple way for running a Devfile Command
  • additional features, like opening the command's output, terminating or rerunning, etc.

Describe alternatives you've considered

No response

Additional context

VS Code provides Tasks API for the extensions:
https://code.visualstudio.com/api/references/vscode-api#tasks

@azatsarynnyy azatsarynnyy added kind/enhancement A feature request - must adhere to the feature request template. severity/P2 Has a minor but important impact to the usage or development of the system. team/editors area/editor/vscode Issues related to the Code OSS editor of Che labels Sep 14, 2022
@azatsarynnyy azatsarynnyy changed the title Side panel for Devfile Commands VS Code side panel for Devfile Commands Sep 14, 2022
@che-bot
Copy link
Contributor

che-bot commented Jun 7, 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 Jun 7, 2023
@che-bot che-bot closed this as completed Jun 14, 2023
@azatsarynnyy
Copy link
Member Author

With the extensions like Task Manager the UX for running the Devfile Commands is a bit better. Nevertheless, there're much more we can do for making it much more convenient. So, reopening the issue.

@azatsarynnyy azatsarynnyy reopened this Jun 15, 2023
@che-bot che-bot closed this as completed Jun 22, 2023
@azatsarynnyy
Copy link
Member Author

/remove-lifecycle stale

@azatsarynnyy azatsarynnyy reopened this Jun 22, 2023
@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 22, 2023
@ddoan
Copy link

ddoan commented Jul 19, 2023

Does reopening this issue have any indication on when it will be prioritized? I'd like to add a vote for it.

@azatsarynnyy
Copy link
Member Author

azatsarynnyy commented Jul 31, 2023

AFAIK, it's not among the nearest priorities of our team. But contributions are welcomed, of course )
I've reopened it just to reflect that it's still relevant.

@che-bot
Copy link
Contributor

che-bot commented Jan 27, 2024

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 Jan 27, 2024
@che-bot che-bot closed this as completed Feb 3, 2024
@azatsarynnyy
Copy link
Member Author

/remove-lifecycle stale

@azatsarynnyy azatsarynnyy reopened this Feb 5, 2024
@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 5, 2024
@Mbd06b
Copy link

Mbd06b commented May 2, 2024

Took me a while to figure out how to access devfile defined commands from the VS Code editor default. Just an alternative, a little higher-visibility on some documentation somewhere might help too.

@azatsarynnyy
Copy link
Member Author

Thanks @Mbd06b. It's a good point. I reopened #21835 and #21841.

@azatsarynnyy
Copy link
Member Author

I've just come up with an idea on how to make it as simple as possible, probably.
@Mbd06b WDYT if we add a new command to the Eclipse Che menu
image
which is opened by clicking the bottom-left button
image

The command would be Eclipse Che: Run Devfile Command...
It would open the list of the Devfile Commands
image
already filtered by devfile type.
It would do the same as the Terminal > Run Task... > devfile, but the user can find it in a much more expected place.

@Mbd06b
Copy link

Mbd06b commented Aug 29, 2024

Sorry it's been a long time replying. I think that finding links to those built-in commands was what I was expecting by default from the che menu. Even if it links over to some kind of context as to how those are defined or triggered would be helpful, so the UI helps self-document how predefined devfile commands can be used.

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 kind/enhancement A feature request - must adhere to the feature request template. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

5 participants