microsoft / microsoft/java-debug
Use client agnostic command names
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 409
- Forks
- 204
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 4
Description
From https://github.com/eclipse/eclipse.jdt.ls/pull/424#issuecomment-344130840, I noticed the debugger exposes vscode* commands on the server side.
[Trace - 21:52:28] Received request 'client/registerCapability - (5)'.
Params: {
"registrations": [
{
"id": "18163e21-97e7-4ae8-b51c-5cdb20e639b1",
"method": "workspace/executeCommand",
"registerOptions": {
"commands": [
"java.edit.organizeImports",
"vscode.java.fetchUsageData",
"vscode.java.resolveClasspath",
"vscode.java.resolveMainClass",
"vscode.java.updateDebugSettings",
"vscode.java.buildWorkspace",
"vscode.java.startDebugSession"
]
}
}
]
It'd be better if the names were client agnostic.
Contributor guide
No contributing guide indexed for this repository
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 locating where the listed workspace/executeCommand names are registered and used, including the vscode.java.* commands shown in the issue. Determine the project's client-neutral naming convention, update the registrations and references consistently, and verify that command registration still works for the Java debug server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100