Skip to content
This repository has been archived by the owner on Aug 31, 2023. It is now read-only.

lsp-proxy vs lsp_proxy #4489

Closed
ematipico opened this issue May 16, 2023 Discussed in #4487 · 1 comment · Fixed by #4491
Closed

lsp-proxy vs lsp_proxy #4489

ematipico opened this issue May 16, 2023 Discussed in #4487 · 1 comment · Fixed by #4491
Assignees
Labels
A-CLI Area: CLI S-Bug: confirmed Status: report has been confirmed as a valid bug

Comments

@ematipico
Copy link
Contributor

Discussed in #4487

Originally posted by kkkrist May 16, 2023
v12.1.0 seems to have changed the lsp-proxy command to lsp_proxy (hyphen vs. underscore). Is this intentional? The docs still use the hyphen. In any case, it breaks some editor integrations (nvim-lspconfig). Do downstream project need to adapt?

$ ~/bin/rome-12.1.0 lsp-proxy
flags/invalid ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ Failed to parse CLI arguments.
    
    Caused by:
      No such command: `lsp-proxy`, did you mean `lsp_proxy`?
```</div>
@ematipico ematipico added S-Bug: confirmed Status: report has been confirmed as a valid bug A-CLI Area: CLI labels May 16, 2023
@dsully
Copy link

dsully commented May 16, 2023

+1 - LSP integration stopped working for me as well due to this backwards incompatible change.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-CLI Area: CLI S-Bug: confirmed Status: report has been confirmed as a valid bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants