No way to provide arguments for after `lsp`
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 80
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
hh_client makes a distinction between global options and per-command options. For example, hh_client --enhanced-hover lsp is invalid, but hh_client lsp --enhanced-hover is valid
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 how the VS Code extension invokes hh_client for the lsp command and how command arguments are assembled. Verify the handling of global versus per-command options, then confirm that an option such as --enhanced-hover can be passed after lsp without producing an invalid command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100