mask VS structopt

Another alternative I'll add is my mask CLI tool. It reads a markdown file and parses it for a command structure. Markdown code blocks are used to define bash/zsh/python/ruby/node scripts all within a single file.

I also build and maintain a Rust-based CLI tool called mask. While this doesn't run in production, it powers everything from my local development workflow to my CI and production deployment flow.

It is a new project that is currently in Alpha stage. You can download from my GitHub account and play with it. It is built using Svelte, Nw.js, and mask script running.

I mentioned elsewhere in this thread that I built a jigsaw puzzle website [1] with a Rust API backend and I launched it last week. It definitely took longer than if I had used Node, but I enjoy working with Rust much more.

Apart from that website, I have also open sourced a Rust CLI task runner [2] which uses markdown files as a command definition format. This is probably the most important tool I've ever written, as I have used it every single day since.

[1]: https://puzzlepanda.com

[2]: https://github.com/jakedeichert/mask

At the top level, there are three things: the server directory, the UI directory, and a maskfile.md file for using mask. Mask is a great tool for running scripts on your project. I use it all the time.

Hope you are aware that structopt is in maintenance mode and is merged into clap as of v3.

As I understood you need to implement a command line argument parser for that you can use clap https://github.com/clap-rs/clap or structopt https://github.com/TeXitoi/structopt.

I feel like discovering moves like this is a weakness in the ecosystem today. You can check out some of our discussion on raising visibility

Something I've been giving thought to is how to help structopt users discover that clap3 is their upgrade path. We've put notices in the structopt repo but cargo upgrade and docs.rs won't say anything. See https://github.com/TeXitoi/structopt/issues/525 for more ideas we're considering.

For myself, I have found serde.rs really useful for undertanding their derives while I've always been frustrated with finding anything in structopt's documentation, so I modeled it more off of serde. This ended up both being in structure and not being in docs.rs. I think it really was the structure that was the frustration point for me but there was interest elsewhere in moving stuff out of docs.rs.

I think it would be nice to have a comparison to clap-derive and/or structopt in the README, as that is what I expect most users would compare this to. The subcommand handling looks especially cumbersome compared to deriving on structs and enums.

However, the one place I'm a little curious to rewrite things is the CLI... every time we have to deal with cobra I long for Rust's structopt.

Have you tried https://github.com/TeXitoi/structopt ?

It is written in Rust using the structopt and swayipc crates. It is published on crates.io. The repository is hosted on GitLab. The repository is mirrored on GitHub.

I use structopt, which itself uses clap.