Closed lgarron closed 1 year ago
From the rage
command I can see that the Rome server used by the LSP must be older than the 10.0 version as it doesn't support the rage command.
Can you try running npx rome stop
to force a restart of the Rome LSP. It is a known limitation that you must restart Rome after updating it in the package.json
Can you try running
npx rome stop
to force a restart of the Rome LSP.
This somehow seems to prevent the extension from properly working at all, even after a full VSCode restart. If I mangle some code enable verbose trace logging, I see messages like the following in the trace log, but they are not highlighted in the VSCode editor at all.
[Trace - 11:23:04 PM] Received response 'textDocument/codeAction - (14)' in 4ms.
Result: [
{
"edit": {
"changes": {
"file:///Users/lgarron/Downloads/sdkfljdsf/cubing.js/src/sites/experiments.cubing.net/cubing.js/speechcubing/index.ts": [
{
"newText": " {",
"range": {
"end": {
"character": 19,
"line": 84
},
"start": {
"character": 19,
"line": 84
}
}
},
{
"newText": "}\n ",
"range": {
"end": {
"character": 6,
"line": 88
},
"start": {
"character": 6,
"line": 88
}
}
}
]
}
},
"kind": "quickfix",
"title": "Wrap the statements in a block"
}
]
npx rome rage
does seem to show it successfully using v10.0.0 of the CLI, but I'd have to manually redact the full output before sharing.
npx rome rage does seem to show it successfully using v10.0.0 of the CLI, but I'd have to manually redact the full output before sharing.
You can share the output of rome rage
without the logs attached. That may already be helpful to understand if we are running into a version mismatch or not.
π @rome/staff please triage this issue by adding one of the following labels: S-Bug: confirmed
, S-Planned
, S-Wishlist
or umbrella
Now that the CLI is able to use the version of Rome from node_modules
, I no longer run into this issue.
Environment information
What happened?
Now, the CLI halts on the following "unknown" rules, which were previously valid:
corectness/useSimplifiedLogicExpression
nursery/noUnusedVariables
Removing those from
rome.json
allows the CLI to run, but now it expectscorrectness/useTemplate
to be calledstyle/useTemplate
on this line: https://github.com/cubing/cubing.js/blob/0f0d36c7b88458e326f5754338ae01296dbe3383/src/sites/experiments.cubing.net/cubing.js/speechcubing/index.ts#L39 However, changing that line to use// rome-ignore lint(style/useTemplate)
now causes the Rome VSCode extension to make therome-ignore
comment rule as unknown, and the relevant code to be marked with an error.Also see: https://github.com/rome/tools/issues/3507#issuecomment-1293122392
Expected result
The CLI and the extension agree on rules.
Ideally, they would also do one of the following:
Alternatively, it would be nice to be able have the extension use the CLI from
node_modules
, so that they're always consistent: https://github.com/rome/tools/discussions/3218Code of Conduct