redhat-developer / redhat-developer/vscode-java
Register diagnostic related commands at beginning
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
As the thing happens in https://github.com/redhat-developer/vscode-java/issues/2589.
The extension failed to start before the diagnostic related commands registration. So, nothing happens when the user clicks Clean and Restart.
We need to consider registering those diagnostic related commands (clean cache, open logs, ...) at the beginning of the extension activation.
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 extension activation entry point and the registration paths for the diagnostic commands named in the issue, including Clean and Restart, clean cache, and open logs. Verify when registration occurs relative to startup failure handling, then confirm that these commands remain available when activation fails early.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100