We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, I'm using https://github.com/rust-lang/rfcs/blob/master/text/1525-cargo-workspace.md
It would be awesome to be able to pick a "member" project for a cargo command (or even just change the cargo command working directory).
At the moment I'm working around the issue by just opening up my "members" in a different IDE window.
You can reference https://github.com/habitat-sh/habitat for a production example.
The text was updated successfully, but these errors were encountered:
Yep, this is a known pain point. The best workaround currently would be to specify --manifest-path flag for each run configuration.
--manifest-path
I intend to fix this in Cargo: currently if you run cargo test --package foo in the root of the workspace, you get the "virtual manifest error".
cargo test --package foo
Sorry, something went wrong.
upstream issue: rust-lang/cargo#3194
Moved to the plugin repo: intellij-rust/intellij-rust#733
No branches or pull requests
Hi, I'm using https://github.com/rust-lang/rfcs/blob/master/text/1525-cargo-workspace.md
It would be awesome to be able to pick a "member" project for a cargo command (or even just change the cargo command working directory).
At the moment I'm working around the issue by just opening up my "members" in a different IDE window.
You can reference https://github.com/habitat-sh/habitat for a production example.
The text was updated successfully, but these errors were encountered: