rust-lang / rust-lang/rust-analyzer
VS Code multi project workspace information
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
I'm new to rust and ran into an issue with the rust-analyzer being indicated as active by vs code but not actually doing anything because I had set up the directory incorrectly. I had a root git folder with two separate rust projects in it.
|-Root
|--- Project a
|--- Project b
I had previously been experimenting with vim so I was running from the projects roots separately, but when I returned to vs code the lsp stopped working. I now know that this is because I had not set up the root correctly to tell the lsp about the structure but, it didn't give any information about what the problem was or that there even was one. It was only when I deleted one of the projects and reloaded that the lsp gave an error.
It would be nice if there was a pop-up or print out to inform about the issue to give some clue to newbies about what was wrong. Perhaps even going as far as activating the red highlighting on the lsp indicator to show that it is not active.
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 investigating rust-analyzer's multi-project workspace handling in VS Code and how failures are surfaced. The issue provides no file, test, or entry point; done would mean a clear user-facing indication when the workspace is configured incorrectly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, vscode
- Domain
- developer-experience, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100