rust-lang / rust-lang/rust-analyzer

can't detect crate changes.

Open
#11,994 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-cargo C-bug S-unactionable
Dominant language
Rust
Stars
16.9k
Forks
2.2k
Avg merge
1d 12h
Merged PRs (30d)
72

Description

My project consist of several my own crates. After any changes in any crate my project dependent of I need to reload vscode for rust analiser detect changes or it remain error for forever.
Is there a way to ask analiser auto scan changes in dependencies crates? Without it...develop several crates is a pain

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the report in VSCode with a project containing multiple local Rust crates, changing one dependency while rust-analyzer is running. Investigate how rust-analyzer notices dependency changes and compare that behavior with reloading VSCode; done means dependent crates update without a manual reload and the behavior is covered by a regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.