redhat-developer / redhat-developer/lsp4ij
Append command name to workspace/executeCommand trace
Open
Nobody has claimed this yet.
enhancement
good first issue
- Dominant language
- Java
- Stars
- 344
- Forks
- 113
- Avg merge
- 5h 22m
- Merged PRs (30d)
- 15
Description
It'd be convenient to directly see which command is executed on workspace/executeCommand, without having to set verbose trace and open specific message item
I'd like to see this instead:
[Trace - 16:14:46] Sending request 'workspace/executeCommand [gopls.reset_go_mod_diagnostics] - (62)'.
Params: {
"command": "gopls.reset_go_mod_diagnostics",
"arguments": [
{
"URI": "file:///Users/fbricon/Dev/souk/IdeaProjects/lsp4ij-tests/untitled/src/go.mod",
"DiagnosticSource": ""
}
]
}
[Trace - 16:14:46] Received response 'workspace/executeCommand [gopls.reset_go_mod_diagnostics] - (62)' in 2ms.
No result returned.
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 locating the trace formatting entry point for workspace/executeCommand requests and responses. Check how the command parameter is currently represented, then verify that both trace lines include the command name and that the existing trace output remains valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100