-
Couldn't load subscription status.
- Fork 1.9k
Open
Labels
Broken WindowBugs / technical debt to be addressed immediatelyBugs / technical debt to be addressed immediately
Description
Hello,
Since a couple of days (probably the merge of #20806), rust-analyzer creates a target folder in the root of my git repository with the following tree:
target
└── rust-analyzer
└── rust-analyzer
└── flycheck0
├── stderr
└── stdout
The root of my repo is not a Cargo project/workspace, I only have a rust project in a sub folder (which contains the expected target/rust-analyzer folder). I'd expect the flychecks to be placed in the existing path/to/cargo_project/target folder.
This will be annoying for users as if not ignored by .gitignore, this will produce a new folder automatically that may be committed by mistake.
Relevant options
rust-analyzer.cargo.targetDir:truerust-analyzer.linkedProjects:[ "path/to/cargo_project/Cargo.toml" ]
Env
- VSCode Extension nightly
- Ubuntu 22.04
roblourens, Vlad-Shcherbina, ia0, teobouvard, P3EDH7 and 14 more
Metadata
Metadata
Assignees
Labels
Broken WindowBugs / technical debt to be addressed immediatelyBugs / technical debt to be addressed immediately