rust-analyzer.linkedProjects doesn't work with relative path, ${workspaceFolder}. Is there any workaround?

Question

I have a repository that has a Cargo.toml in sub_dir/Cargo.toml (Cargo.toml is not in repository root directory)
I'm using the repository from some of my computers. So I need to set up rust-analyzer.linkedProjects by each environment...

I want to avoid the configuration by machine. Do you know anything workaround?

score 9 · Accepted Answer · edited Mar 02 '23 at 16:31

9

to .vscode/settings.json

"rust-analyzer.linkedProjects": [
  "relateive/path/to/the/project/directory",
]

should add the path to Cargo.toml, like this.

"rust-analyzer.linkedProjects": [
  "relateive/path/to/the/project/directory/Cargo.toml",
]

edited Mar 02 '23 at 16:31

jps

20,041
15
75
79

answered May 19 '22 at 17:43

ozkanpakdil

3,199
31
48

I spent so much time on this. The wording of the error message is really bad. – Boiethios Feb 28 '23 at 12:18

score 1 · Answer 2 · answered Mar 02 '23 at 16:27

1

In .vscode/settings.json set the "rust-analyzer.linkedProjects" point to your Cargo.toml using an absolute path. That's the only way I got it to work eventhough all the resources online tend to tell you to use a relative path.

"rust-analyzer.linkedProjects": [
  "absolute/path/to/the/project/Cargo.toml"
],

answered Mar 02 '23 at 16:27

mmatila

76
6

I had to use a absolute path as well. For example in your .vscode/settings.json you would put "backend/rust_project/Cargo.toml" for a a tree structure as backend->rust_project from the root folder. – Vraj Shah Apr 10 '23 at 02:44

rust-analyzer.linkedProjects doesn't work with relative path, ${workspaceFolder}. Is there any workaround?

2 Answers2