redhat-developer / redhat-developer/vscode-openshift-tools
Components view not visible enough
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 123
- Forks
- 63
- Avg merge
- 6h 16m
- Merged PRs (30d)
- 74
Description
When I open the plugin view, the views on left bar are, in this order:
- Application Explorer
- Components
- Devfile Registries
- Debug Sessions
As a developer, I would expect that the Components view is the first one in the list, as this is the first one I want to focus on: I first need to "Start Dev" from the Components view before there are any information available in the "Application Explorer".
This is especially true when running on podman, where the Application Explorer is not necessary.
I understand that the dev needs to connect to a cluster before to be able to work, but this should, IMHO, be triggered by an alert (pop-pu, etc) and not by the fact that the Application Explorer is first in the list.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the VS Code plugin view and its left-bar ordering for Application Explorer, Components, Devfile Registries, and Debug Sessions. Check how the Components view is registered and how the Application Explorer handles cluster connection prompts. Done means Components appears first and the view order and connection behavior match the issue’s expectation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, typescript, vscode
- Domain
- developer-experience, devtools
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100