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

rome lsp-proxy no longer takes --config-path #4505

Closed
1 task done
dsully opened this issue May 17, 2023 · 0 comments · Fixed by #4509
Closed
1 task done

rome lsp-proxy no longer takes --config-path #4505

dsully opened this issue May 17, 2023 · 0 comments · Fixed by #4509
Assignees
Labels
A-CLI Area: CLI S-Bug: confirmed Status: report has been confirmed as a valid bug

Comments

@dsully
Copy link

dsully commented May 17, 2023

Environment information

$ rome rage
CLI:
  Version:                      12.1.1
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  ROME_LOG_DIR:                 unset
  NO_COLOR:                     unset
  TERM:                         "wezterm"
  JS_RUNTIME_VERSION:           "v18.14.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "null"

Rome Configuration:
  Status:                       unset

Workspace:
  Open Documents:               0

What happened?

Prior to the issue in #4489, rome lsp-proxy --config-path /path/to/config/ used to work.

Expected result

rome lsp-proxy --config-path /path/to/config/ should work and load the rome.json file in the specified path.

Code of Conduct

  • I agree to follow Rome's Code of Conduct
@dsully dsully added the S-To triage Status: user report of a possible bug that needs to be triaged label May 17, 2023
@ematipico ematipico added S-Bug: confirmed Status: report has been confirmed as a valid bug A-CLI Area: CLI and removed S-To triage Status: user report of a possible bug that needs to be triaged labels May 17, 2023
@ematipico ematipico self-assigned this May 17, 2023
@ematipico ematipico mentioned this issue May 18, 2023
3 tasks
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