rust-lang / rust-lang/rust-analyzer
`rust-project.json` generation does not index `rust-dependencies`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Rules Rust Issue
Settings.json - Visual Studio Code
Platform Details
| Component | Version | Latest |
|---|---|---|
| OS | Windows 11 | ✅ |
| Bazel Version | 8.1.1 | ✅ |
| Rules Rust | 0.59.2 | ✅ |
Other versions are latest stable and tied to project setup.
Issue
Since around October of last year (did not bisect issue yet precisely, uncertain if it is a windows, rules_rust, or rust-analyzer issue), the rust-analyzer plugin and the rust-project.json file generated by Bazel have stopped correctly identifying and indexing dependencies for the Rust project in our repository. Inspecting the file system and cargo information manually for issues was not clear for me.
Reproduce
- Plugin load for
rust-analyzerlanguage service with generatedrust-project jsonwithbazel run config=analysis - Observe,
Rust Dependenciesnot indexing any crates included inspecor local sources files inMoltensubmodule.
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 reproducing the issue with the rust-analyzer plugin and the generated rust-project.json using bazel run config=analysis, then inspect the provided rust-project.json and the linked Rules Rust issue. Done means dependencies from spec and local sources in the Molten submodule are correctly indexed under Rust Dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100