-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 new: automatically add to workspace #10670
Labels
C-feature-request
Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
Comments
theduke
added
the
C-feature-request
Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
label
May 15, 2022
Thanks for the report. This is a known issue, closing as a duplicate of #8365. |
@ehuss these are two different requests. The other issue is about creating an empty workspace. This issue is about automatically modifying the members declaration in a workspace when running 'new' inside a workspace. |
Sorry, I should have linked to #6378. |
Any news about this proposal ? What's the current situation ? Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-feature-request
Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
Problem
When running
cargo new
in a workspace a warning is printed, but you have to manually add the new crate to themembers = []
section.Proposed Solution
Add a new
--workspace
/-w
flag tocargo new
that automatically adds the new crate with the correct path tomembers
.Print a hint about the flag when
cargo new
is run in a workspace.This is admittedly a small quality of life feature, but I do it often enough that it becomes annoying.
The text was updated successfully, but these errors were encountered: