-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cargo.toml files using absolute paths are not correctly parsed #2434
Comments
I did try to replicate your case with a full path deps and but it did works : # /sandbox/temp/foo/crates/foo.toml
[package]
name = "foo"
version = "0.1.0"
edition = "2018"
[dependencies]
baz = {path="/sandbox/temp/foo/crates/baz"} Would you mind to just share the post-generated Cargo.toml ? |
Haven't looked into this yet, but an interesting thing for Fuchsia use-case is that we don't require a In theory, producing something like |
|
@gbbosak The following are just my guesses: Did any Maybe that Cargo.toml in BTW, I would recommend to discuses in RA Zulip Channel. |
We're looking into whether or not emitting a rust-project.json file would be feasible. I'll update this when I find out the results of that. |
We've switched to rust-project.json and it works now. Closing this bug. |
On Fuchsia; we use a gen-cargo script to generate Cargo.toml files from our custom build system that are compatible with RLS. These files use absolute paths to their dependencies, and this seems to break rust-analyzer, but functions just fine with RLS.
Steps to repro:
when trying to navigate between files with rust-analyzer.
The text was updated successfully, but these errors were encountered: