rust-lang / rust-lang/rust-analyzer

[feature request] [vs-code] Use new `files.readonlyInclude` for external crates

Open
#15,015 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-vscode C-feature
Dominant language
Rust
Stars
16.9k
Forks
2.2k
Avg merge
1d 12h
Merged PRs (30d)
72

Description

Go to Definition opens the source files for the standard library and external crates, where a missclick could change them.
The new setting files.readonlyInclude with

"files.readonlyInclude": {
    "C:/Users/anton/.rustup/**/*": true,
    "C:/Users/anton/.cargo/**/*": true,
}

where the correct locations are automatic generated would prevent mistakes.

I would appreciate if the extension could change the user setting automatic. Maybe a small question, when the extension is activated with yes, no and never.

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

No files or tests are named. Start by locating the Go to Definition handling for standard-library and external-crate sources, then inspect the extension activation and settings paths; done means the relevant generated locations are covered by files.readonlyInclude with a clear yes/no/never choice.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust, vscode
Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.