redhat-developer / redhat-developer/vscode-openshift-tools
Make the loading of the Views in some order so that extension activation is faster
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 123
- Forks
- 63
- Avg merge
- 6h 16m
- Merged PRs (30d)
- 74
Description
Currently when OpenShift extension is started, the Activation time is too long and all the views are in refresh state at same time. This delays the Activation and users have to wait to even Login.
We need to device a strategy of loading the view in some particular order so that Activation is faster and Application Explorer View is loaded first. Once that view is ready, in background we can load the other views.
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 at the extension activation entry point and trace how the Application Explorer View and the other views enter their refresh state. Define an activation order that makes Application Explorer ready first and moves the remaining views to background loading. Done means activation no longer waits for all views and users can reach Login sooner.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100