committed
clap-rs
committed | clap-rs | |
---|---|---|
5 | 154 | |
94 | 13,327 | |
- | 1.6% | |
7.9 | 9.5 | |
3 days ago | 5 days ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
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.
committed
-
Any good alternative to husky in rust to enforce and write conventional commits and for pre-commit source code linting??
I use https://github.com/crate-ci/committed and pre-commit (the python app)
-
[Gitoxide December Update]: a new object database and upcoming multi-pack index support
committed just reads commit messages between a range of commits, after resolving refs
-
Ouch 0.3.0 released!
For colors, I've found yansi to be great to work with. I then use concolor-control (example) and `concolor-clap (no clap3 support yet, example part 1 and example part 2). As you can see, I also like to organize my colors by the styling role they fill. The only reason I wrapped in that example is its part of the crate's API and didn't want the public API tied to yansi.
-
Git-cliff: generate changelog files from the Git history
While auto-generated changelogs aren't the best, they are better than nothing. Too often I've seen projects without a changelog which is especially annoying when dealing with breaking changes.
I've been considering switching to a changelog generator, either from Conventional Commits or from a folder of files just to avoid merge conflicts with the CHANGELOG file.
If people want enforcement of Conventional Commit, check out https://github.com/crate-ci/committed
- Committed – A commit message linter optionally supporting conventional commits
clap-rs
-
Build Your Own curl - Rust
We will be using the library for Clap - A simple-to-use, efficient, and full-featured library for parsing command line arguments and subcommands.
-
CLI Contexts
I recently came across this question (and associated answer) on the clap repository. The answer given is a good one. But I wanted to expand with my own findings and practices, which spurred the motivation for this post.
-
Getting Started with CLI tools in Rust using Clap
We can also use tuple-like struct syntax and named-field struct syntax for enum variants within our enum; this is because unlike in other OOP languages, Rust enums are actually sum types. You can read more about how powerful Rust enums are in another article we wrote here. You can have optional arguments by simply wrapping the types in Option, but if you want to add a flag to a command you can use bool, since clap recognises that flags are either there or not there. Let's have a look at what this might look like:
-
Flow Updater JSON Creator
I began by developing a wrapper for the CurseForge API, which turned out to be a lengthy and challenging process but constituted the bulk of the work. Next, I coded the CLI, which was relatively straightforward. Instead of using the clap crate, a Rust tool for generating CLIs, I opted for the following line of code:
-
netcrab: a networking tool
By this time I had already gotten tired of parsing arguments by myself and had looked for something to help with that. I found a really dang good argument parsing library called clap. What makes it so cool is it's largely declarative for common uses. You simply mark up a struct with attributes, and the parser automatically generates the usage and all the argument parsing code.
-
Grimoire - A recipe management application.
How CLI arguments are handled (using clap).
- Rust 1.72.0
-
I made an alternative --help renderer for clap based applications
Is this just referring to wrapping based on the terminal width? That is supported with the wrap_help feature though I have been considering making it a default feature.
-
Looking for advice around project direction using artix-web
CLI, use Clap. If you want to get fancy, use Tui.
-
Build a HTTP server with Rust and tokio - Part 1: serving static files
As our CLI is getting more complex, we'll use the clap crate to parse the command line arguments.
What are some alternatives?
auto-changelog-action
structopt - Parse command line arguments by defining a struct.
onefetch - Command-line Git information tool
argh - Rust derive-based argument parsing optimized for code size
gitoxide - An idiomatic, lean, fast & safe pure Rust implementation of Git
docopt.rs - Docopt for Rust (command line argument parser).
git-hooks.nix - Seamless integration of https://pre-commit.com git hooks with Nix.
argparse-benchmarks-rs - Collected benchmarks for arg parsing crates written in Rust [Moved to: https://github.com/rosetta-rs/argparse-rosetta-rs]
GitHub Changelog Generator - Automatically generate change log from your tags, issues, labels and pull requests on GitHub.
easy_flag - Simple command line flag parser for rust.
gnulib - upstream mirror
serde - Serialization framework for Rust