-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Very slight cargo add
documentation improvements
#11033
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Very slight cargo add
documentation improvements
#11033
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @ehuss (or someone else) soon. Please see the contribution instructions for more information. |
Oops, looks like I edited the wrong file. Looking into this. EDIT: resolved. |
f5f8c5f
to
7d7e0fa
Compare
This is a common problem. We should consider if there are ways to better point users to what to edit |
Yes, putting all the generated files into a Btw I am extremely touched that you consider my mistake an opportunity to improve the contribution process! |
0853879
to
cf4fe85
Compare
This refers to the `Features` part of the message that gets printed to stderr after successfully adding some dependency, e.g.: ``` cargo add my-crate Updating crates.io index Adding my-crate v0.1.0 to dependencies. Features: + foo - bar ``` This tells us that the `foo` feature is enabled and `bar` is disabled.
cf4fe85
to
9c8a8ea
Compare
@bors r+ Thanks! |
☀️ Test successful - checks-actions |
RE Improving the experience I have two ideas:
|
Hmm, directory rename won't work as well as I expected because I forgot how things are laid out. |
The goal is to help new (and existing) users more quickly find the appropriate files to edit (like in rust-lang#11033). The main downside is for someone trying to find output to verify what it looks like, a simple search won't turn up results but there are other ways around that (`--no-ignore`, `git status` after doing a man generation, etc).
chore: Don't show genned docs in ripgrep The goal is to help new (and existing) users more quickly find the appropriate files to edit (like in #11033). The main downside is for someone trying to find output to verify what it looks like, a simple search won't turn up results but there are other ways around that (`--no-ignore`, `git status` after doing a man generation, etc).
8 commits in 4ed54cecce3ce9ab6ff058781f4c8a500ee6b8b5..646e9a0b9ea8354cc409d05f10e8dc752c5de78e 2022-08-27 18:41:39 +0000 to 2022-09-02 14:29:28 +0000 - Support inheriting jobserver fd for external subcommands (rust-lang/cargo#10511) - refactor(cli): Lazy load config (rust-lang/cargo#11029) - chore: Don't show genned docs in ripgrep (rust-lang/cargo#11040) - Document private items for Cargo and publish under contributor guide (rust-lang/cargo#11019) - Add names to CI jobs (rust-lang/cargo#11039) - Rework test error handling (rust-lang/cargo#11028) - Very slight `cargo add` documentation improvements (rust-lang/cargo#11033) - Update compiling requirements. (rust-lang/cargo#11030)
Update cargo 8 commits in 4ed54cecce3ce9ab6ff058781f4c8a500ee6b8b5..646e9a0b9ea8354cc409d05f10e8dc752c5de78e 2022-08-27 18:41:39 +0000 to 2022-09-02 14:29:28 +0000 - Support inheriting jobserver fd for external subcommands (rust-lang/cargo#10511) - refactor(cli): Lazy load config (rust-lang/cargo#11029) - chore: Don't show genned docs in ripgrep (rust-lang/cargo#11040) - Document private items for Cargo and publish under contributor guide (rust-lang/cargo#11019) - Add names to CI jobs (rust-lang/cargo#11039) - Rework test error handling (rust-lang/cargo#11028) - Very slight `cargo add` documentation improvements (rust-lang/cargo#11033) - Update compiling requirements. (rust-lang/cargo#11030)
The goal is to help new (and existing) users more quickly find the appropriate files to edit (like in rust-lang#11033). The main downside is for someone trying to find output to verify what it looks like, a simple search won't turn up results but there are other ways around that (`--no-ignore`, `git status` after doing a man generation, etc).
The goal is to help new (and existing) users more quickly find the appropriate files to edit (like in rust-lang#11033). The main downside is for someone trying to find output to verify what it looks like, a simple search won't turn up results but there are other ways around that (`--no-ignore`, `git status` after doing a man generation, etc).
As discussed in rust-lang/book#3331, a quick explanation of the
Features
part of the message that gets printed to stdout when adding some dependency.Consider the following example:
It was not clear to me what
+foo
and-bar
meant until @carols10cents' kindly explained it to me. Hopefully the documentation now clarifies this.TODO:
./build-man.sh