argh
cli-guidelines
argh | cli-guidelines | |
---|---|---|
7 | 47 | |
1,568 | 2,788 | |
1.6% | 0.9% | |
6.0 | 3.6 | |
21 days ago | about 1 month ago | |
Rust | CSS | |
BSD 3-clause "New" or "Revised" License | Creative Commons Attribution Share Alike 4.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.
argh
-
Crate List - Blessed.rs
https://github.com/google/argh is another minimal library for CLI argument parsing that could be in the list
-
Rust Web Framework Comparison
My go-to is argh[1], as it's more lightweight while still providing a nice derive-based API.
[1]: https://github.com/google/argh
-
Immediately off the top of your head what is the best Rust CLI library.
It'll panic if the path contains non-UTF8-able bytes.
-
fncmd: Command line interface as a function.
Yes clap needs a lot of boilerplate that small programs don't always need, but if you're going to simplify it, I don't think having a bunch of arguments given to the main function is better than having an option struct as in argh. Such an option struct can be given to other functions from the main, can have dedicated consistency check or completion methods, etc.
-
Newbie frustration: can we KISS more?
Typically programs are configured through a config object. People like to use things like clap, structopt, or argh for passing in arguments through the CLI https://github.com/google/argh. You can also use the env! macro for embedding values in at compile time, or by going through the std::env::var infrastructure for runtime env vars.
-
Darkroom: A VCR contract testing tool built in Rust
Until the argh crate bumps their version I cannot updater the version on crates.io so the install command currently is: cargo install --git https://github.com/mkatychev/darkroom
-
Announcement: xflags, fast-to-compile proc macro for cli args
Ahh. The secondary reason I discounted Argh as "unsuitable for purpose" after "Doesn't support using OsString under the hood".
cli-guidelines
- Ask HN: Where to read about terminal UIs?
-
Ask HN: Do you read Secrets from Environment Variables
The Command Line Interface Guidelines [1] says:
> Do not read secrets from environment variables
> Secrets should only be accepted via credential files, pipes, `AF_UNIX` sockets, secret management services, or another IPC mechanism
Which one of these do you use? On github it seems common for projects to use environment variables for secrets.
[1] https://clig.dev/#environment-variables
-
Command Line Interface Guidelines
Seems they took a small step back from their previous "don't bother with man pages" stance. Now it's "Consider providing man pages."
I still find it a rather shocking order of priority, honestly.
https://clig.dev/#documentation
-
Ask HN: Best way to do scoped commands in a CLI app
- E. `blah project foo --edit`
Wondering if there was any guidance on this from the UNIX people. Perhaps scoping should be done using the file system. `cd path/to/project && blah edit`. Like git does with `git --cwd=path/to/project`. Maybe a virtual FS could even be used. Then you wouldn't have to continuously type in the scope with each command. Interesting thinking about how to maintain state in the terminal...thinking about how Python's virtual env bin/activate modifies the shell.
Found an interesting guide here: https://clig.dev/
-
CLI user experience case study
Capturing these guidelines is one of the primary reasons that https://clig.dev/ exists.
-
Introducing my Password Manager project - Seeking Feedback and Contributions
You may want to take a look at various existing CLIs to get inspiration on how they operate, the user feedback loop and the ergonomics on using them. Here is a great website on some CLI structing guidance https://clig.dev/
What are some alternatives?
clap-rs - A full featured, fast Command Line Argument Parser for Rust
redox - Mirror of https://gitlab.redox-os.org/redox-os/redox
structopt - Parse command line arguments by defining a struct.
nodejs-cli-apps-best-practices - The largest Node.js CLI Apps best practices list ✨
hello-actix - Hello, actix!
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
xflags
typer - Typer, build great CLIs. Easy to code. Based on Python type hints.
argparse-benchmarks-rs - Collected benchmarks for arg parsing crates written in Rust [Moved to: https://github.com/rosetta-rs/argparse-rosetta-rs]
pico-args - An ultra simple CLI arguments parser.
picocli - Picocli is a modern framework for building powerful, user-friendly, GraalVM-enabled command line apps with ease. It supports colors, autocompletion, subcommands, and more. In 1 source file so apps can include as source & avoid adding a dependency. Written in Java, usable from Groovy, Kotlin, Scala, etc.