redhat-developer / redhat-developer/vscode-java
Refactor `activate()` to use `await`
Open
Nobody has claimed this yet.
build/infra
debt
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
Refactor the activate function (main entry point to extension) to use await instead of promise chaining and promise constructors.
Why?
- The async logic is currently really hard to read
- The function is > 300 lines of code, and using
asynccould make it shorter - The function contains
asyncpromise executors, which are considered bad since they make error handling hard
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's activate entry point and review its promise chains and promise constructors. Refactor the async flow toward the issue's await goal, then run the project's existing checks to confirm behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100