rust-lang / rust-lang/rust-analyzer
Augment auto-discovered projects with an "extra linked projects" list
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Today, there exists the setting in VS Code called rust-analyzer.linkedProjects which allows the user to manually define the paths to their workspace projects, but doing so opts you out of project auto-discovery.
In my workspace, I have many projects which are all members of the same cargo workspace, and the list is in regular flux, so it's very nice to rely on the auto-discovery feature, however I also have one or two projects which can't be members of the same cargo workspace and as such they are not auto-discovered by Rust Analyzer.
It would be great if there were a way to tell Rust Analyzer about these couple of analyzable projects without having to opt out of auto-discovery. It seems unlikely that the existing setting mentioned above could be used for this purpose since that would probably be a breaking change, but would it be possible to add a second setting such as rust-analyzer.extraLinkedProjects which is an array of project references just like linkedProjects but whose entries are merged with those found by auto-discovery rather than replacing the auto-discovery process?
Thank you for your consideration, cheers!
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 tracing the existing rust-analyzer.linkedProjects configuration and the auto-discovery entry point. Add a separate extraLinkedProjects setting whose project references are merged with auto-discovered projects, while preserving the existing setting's behavior; verify that both manually added and discovered projects are analyzed together.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100