rust-lang / rust-lang/rust-analyzer
Rust analyzer doesn't respect "rust-analyzer.cargo.target" when running tests or debugging
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Rust analyzer doesn't respect "rust-analyzer.cargo.target" when running tests or debugging code (e.g., via the codelens actions).
I'm not sure if this is intentional or if there is another setting for controlling this, but it is a little surprising, since after configuring the "rust-analyzer.cargo.target" setting, all the other interactive features like completion work as expected for the specified target.
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 configuring rust-analyzer.cargo.target and reproducing the behavior through the codelens actions for running tests and debugging. Compare those actions with interactive features such as completion; done means test and debugging commands use the configured target, or the issue documents why that setting is intentionally not applied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100