cli-guidelines
picocli
Our great sponsors
cli-guidelines | picocli | |
---|---|---|
47 | 29 | |
2,782 | 4,705 | |
2.8% | - | |
3.6 | 8.6 | |
about 1 month ago | 8 days ago | |
CSS | Java | |
Creative Commons Attribution Share Alike 4.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.
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/
picocli
-
GraalVM for JDK 21 is here
Picocli allows using a compiler annotation processor to generate classes at compile time instead [0].
[0]: https://github.com/remkop/picocli/blob/main/picocli-codegen/...
-
Any library you would like to recommend to others as it helps you a lot? For me, mapstruct is one of them. Hopefully I would hear some other nice libraries I never try.
Picocli is a pretty good one for writing CLI apps
-
“Why I develop on Windows”
"and there are simply no good command line input parsing libraries for Java."
Looks like author missed the most obvious and popular OSS one: https://picocli.info/
-
Java 20 / JDK 20: General Availability
The command line example gave me the "ick". It is usually preferrable to parse the command line arguments into one instance of a custom "command class", rather than into a list of things. Like jcommander, picocli or jbock do.
-
any opinion good or bed about a code that smells?
Complex argument parsing needs to be auto-generated by libraries like picocli. Even if you need something custom, it'd be quicker to write an Annotation processor from scratch than editing that file.
-
Owl: A toolkit for writing command-line user interfaces in Elixir
https://github.com/remkop/picocli
"Picocli-based applications can be ahead-of-time compiled to a GraalVM native image, with extremely fast startup time and lower memory requirements, which can be distributed as a single executable file."
https://picocli.info/quick-guide.html
-
Building a Java CLI. How can I make it more powershell-friendly
Using picocli to handle your command line options gives you the best chance to automatically generate an ArgumentCompleter script in the future, but won't help you today (other than possibly making your command line handling more standardized & easier).
-
must known frameworks/libs/tech, every senior java developer must know(?)
Picocli
-
🔍 Validate New-Caledonia Phone Numbers from cli ⌨️
Then we released a JBang! and picocli based cli that would be, on any OS running a jvm runtime :
-
📲 Inspired by Twilio we started to build our own (pico)cli to send sms
picocli : "a mighty tiny command line interface"
What are some alternatives?
redox - Mirror of https://gitlab.redox-os.org/redox-os/redox
Spring Shell 3 - Spring based shell
nodejs-cli-apps-best-practices - The largest Node.js CLI Apps best practices list ✨
JCommander - Command line parsing framework for Java
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
args4j - args4j
typer - Typer, build great CLIs. Easy to code. Based on Python type hints.
Airline - Java annotation-based framework for parsing Git like command line structures
argparse-benchmarks-rs - Collected benchmarks for arg parsing crates written in Rust [Moved to: https://github.com/rosetta-rs/argparse-rosetta-rs]
JLine - JLine is a Java library for handling console input.
cligen - Nim library to infer/generate command-line-interfaces / option / argument parsing; Docs at
JewelCLI - JewelCli uses an annotated interface definition to automatically parse and present command line arguments