concolor
cargo-edit
concolor | cargo-edit | |
---|---|---|
2 | 45 | |
17 | 2,997 | |
- | - | |
0.0 | 7.4 | |
11 months ago | 3 months ago | |
Rust | Rust | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
concolor
-
clap 4.0.0, a Rust argument parser, is released!
concolor-clap
-
Ouch 0.3.0 released!
I'm a little leery of clap taking on the role of color control. I've found that each library with "auto" support does it slightly differently and that really the best place for that policy is in the caller so there is a consistent experience and so it can adapt to the caller's needs. The WG-CLI has talked about this in the past and concolor family of crates is the result. I'm waiting on feedback for termcolor's use case (non-ANSI) before going 1.0 at which point we will probably make this the backend for clap's auto color support.
cargo-edit
-
Hey Rustaceans! Got a question? Ask here (23/2023)!
“cargo add” from https://github.com/killercup/cargo-edit has that behavior, but not the built in one that was added to cargo
-
Is Rust's cargo-edit crate still relevant?
I have also noticed that the last commit of cargo-edit crate's GitHub repo (https://github.com/killercup/cargo-edit) was two days ago (pretty recent.) So it is probably relevant for a lot of people.
-
What are some useful tools for Rust?
cargo-upgrade from cargo-edit (somewhat more intentional than builtin update)
-
How to list upgradable crates programmatically
I've also tried cargo-upgrade from cargo-edit like so:
-
Hey Rustaceans! Got a question? Ask here (9/2023)!
You can also see how other crates do it. For example, cargo-edit is just like that - a single package with a library with a couple of small cli wrappers around it. You can compare their Cargo.toml to yours, maybe there is something different about them.
-
`toml` vs `toml_edit` (ie `toml` 0.6 is out)
Just to check, are you aware of cargo-edit's cargo-set-version or cargo-release?
-
Rust 1.66
Speaking of cargo remove, see also cargo-edit [0] from which adding and removing originally came, as well as cargo-binstall [1] which installs binaries rather than compiling from source every time. The binaries are updatable with cargo-update [2].
The latter two can replace a package manager for Rust related utilities, as I often find that those in OS package repositories are often not as up to date as directly from cargo.
[0] https://github.com/killercup/cargo-edit
[1] https://github.com/cargo-bins/cargo-binstall
[2] https://github.com/nabijaczleweli/cargo-update
-
TIL about cargo add
For context, it was/is part of cargo-edit crate which provides other nice functionalities as well. Hope all gets integrated in time.
-
how can I use same crate but with different features?
https://github.com/killercup/cargo-edit can use the F option
- `cargo-set-version` support for workspace inheritance released in cargo-edit 0.11.4!
What are some alternatives?
argfile - Load additional CLI args from file
nexus-repository-cargo - Nexus Repository Cargo Format
clap-port-flag - Easily add address & port flags to CLIs using Clap
cargo-outdated - A cargo subcommand for displaying when Rust dependencies are out of date
clap-rs - A full featured, fast Command Line Argument Parser for Rust
cargo-do - allows you to run multiple cargo commands in a row
clap-verbosity-flag - Easily add a --verbose flag to CLIs using Clap
Cargo - The Rust package manager
cargo-dot - Generate graphs of a Cargo project's dependencies
cargo-script - Cargo script subcommand
cargo-multi - Extends cargo to execute the given command on multiple crates - upstream is at
cargo-watch - Watches over your Cargo project's source.