redhat-developer / redhat-developer/vscode-openshift-tools
Block some of the component related commands until 'New Component' command finished
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 123
- Forks
- 63
- Avg merge
- 6h 16m
- Merged PRs (30d)
- 74
Description
odo create component-type:version component-name --local /path/to/source
or
odo create component-type:version component-name --git https://github.com/account/repo
are long-running operations that creates multiple OpenShift resources. That allows user to run refresh in OpenShift Explorer and see newly created component in tree. At this point some commands on component does not make sense and should not allowed to be executed until 'New Component' command is finished.
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 tracing the New Component command flow and the handlers for component-related commands. Identify how the extension can represent an in-progress creation, then keep those commands unavailable until the OpenShift resources are created; verify the behavior for both --local and --git forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, typescript, vscode
- Domain
- cloud, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100