rust-lang / rust-lang/rust-analyzer
Custom `rust-analyzer.runnables.test.overrideCommand` breaks `Debug` runnable button
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
With https://github.com/rust-lang/rust-analyzer/issues/21137#issuecomment-4254611341 I now have the following setup:
// `Run Test` and `Run Tests` nextest support
"rust-analyzer.runnables.test.overrideCommand": [
"cargo",
"nextest",
"run",
"--package",
"${package}",
"${target_arg}",
"${target}",
"--",
"${test_name}",
"${exact}",
"${include_ignored}"
],
This seems to break the Debug runnables button
Are they meant to be connected in this manner?
https://github.com/user-attachments/assets/f1b1dd18-2dfa-4c26-861f-a9c6f4f71cbe
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
Reproduce the issue with the shown rust-analyzer.runnables.test.overrideCommand configuration, then compare the Run Test, Run Tests, and Debug runnable button behavior. Trace the runnable handling from the configuration entry point; done means the custom test command still works and the Debug runnable remains available and functions as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100