-
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
VSCode plugin: Add a setting for which subdirectories should be considered Cargo workspaces #3326
Comments
#3309 would pretty much fix this. |
You're right, sorry for the duplicate. |
In case anyone else runs into this, one solution that works for more deeply nested rust crates is to add a |
Can we make #3309 configurable how deep to look? Because now it's either a totally manual |
It's not; you just have to specify |
@flodiebold Do you mean that Exactly:
Thanks! |
Automatic Rustup also fixes rust-lang/miri#3308
Automatic Rustup also fixes rust-lang/miri#3308
Not sure if this is already possible or has been asked before, but how do I handle a project like this?
Currently, the plugin just complains about not finding a Cargo.toml in the workspace root. I know I could just use multiple VSCode workspaces, but I'm not a big fan of that because it would get quite messy in more complex project layouts.
I would suggest adding a
rust-analyzer.cargoWorkspaces
setting to the VSCode plugin that allows one to specify multiple subdirectories which should be considered Cargo workspaces.The text was updated successfully, but these errors were encountered: