redhat-developer / redhat-developer/vscode-java
rewrite extension.ts with async/await instead of then/catch
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
Now we have a more complicated extension.ts than before. I find there're lots of nested then/catch blocks with various callbacks, making the execution order a little bit hard to follow. Maybe we can use async/await style for better readability and clearer flow. What do you think?
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 reading extension.ts and tracing the nested then/catch chains and their callbacks to understand the current execution order. The work is done when the file uses async/await for the same flows without changing observable extension behavior; the issue does not identify tests or a narrower entry point.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100