other languages

中文文档

why this ?

For a long time, developing cli in Rust is difficult. Since Rust is a static language, the compiler needs to know all the details at compile time. It conflicts with the dynamics of the CLI. The community offers a wide range of solutions. Yes, they're excellent, but they're not very simple.

Inspired by commander.js & rocket.rs, the crate was born.

features

• API friendly
• easy to use
• support for approximate dynamic language
• low performance loss
• automatically support for --version & --help
• automatically run corresponding commands

limit

If you want to use this crate, please guarantee that you have follow rules below: + using Rust 2018 (full proc macro support is required, including [procmacro] & [procmacro_attribute]) + using cargo (cargo will produce some environment variable according to Cargo.toml, we need that) + be familiar with Rust (because it's developed for Rust )

As a reference, my versions are: + cargo: cargo 1.35.0-nightly (95b45eca1 2019-03-06) + rustc: rustc 1.35.0-nightly (e68bf8ae1 2019-03-11) + Linux kernal: 4.15.0-47-generic + Ubuntu: 16.04

usage

install commander-rust

Two ways supported: from Github or crates.io. The difference between them is that Github is latest but unstable and crates.io is stable but might not be latest.

install from Github

toml [dependencies.commander_rust] git = "https://github.com/MSDimos/commander_rust" branch = "master"

install from crates.io

toml [dependencies] commander_rust = "1.1.3" # or other version you want to install

using it

We offer a simple but complete example, you can learn all through it. Yes, That's all. Very easy!

```rust

// this is required! Beacuse we used run!(), it's a proc_macro

![feature(procmacrohygiene)]

// Only five items you will use! use commander_rust::{ Cli, command, option, entry, run };

// what's option? what's command? // See commander.js and document of commander-rust for more! // Note, types of parameters are not fixed, any type implemented From<Raw> is valid! // So you can even use rmdir(dir: i32, other_dirs: Vec<i32>, cli: Cli) here. // And Cli is not required! So you can miss it. // See document of commander-rust for more details.

[option(-s, --format , "format output")]

[option(-r, --recursive, "recursively")]

[command(rmdir [otherDirs...], "remove files and directories")]

fn rmdir(dir: String, other_dirs: Option>, cli: Cli) { // If compiler can't give U valid error information, // Consider using a _rmdir function to wrap all of the following code // and then call it here. // See this issue：https://github.com/dtolnay/syn/issues/622

let format = cli.get_or("format", String::new("%s"));

if cli.has("recursive") {
    let quite: bool = cli.get_or("quite", false);

    if quite {
        // silently delete all files
        // just like `rm -rf /`
    } else {
        // tell the world I'm going to delete the files
    }
} else {
    // drink a cup of coffee, relax.
}

}

// options here are public, options above #[command] are private

[option(-q, --quite , "dont display anything")]

[entry]

fn main() { // Run it now!!!!! let app = run!(); // printing app is same as you inputting --help. println!("app is {:#?}", app); } ```

try it

try to input [pkg-name] --help.

version & description & cli-name?

version, description, cli-name of application are from Cargo.toml.

For instance: ```toml

part of Cargo.toml

[package] name = "example-test" version = "0.1.0" description = "Using for test" ```

error

I can't ensure that it will work perfectly in all cases. My abilities are very limited, testing is not my skill and be sorry about that. I'm learning it. So if you find any BUG, please tell me. Thanks.

full example

I offered a full example, it's hash. It's using for generating MD5 of files or strings. See ./examples/for more details.

homepage

I developed homepage for it. See ./homepage for more details. It's developed bashed on React. I like it.

rules

There are several rules you should follow. 1. All #[options] should defined above #[command] and #[entry] 2. DO NOT define options duplicate!!! As a concession, You can define the same option on different command and entry. 3. Private options are visible to specific sub-commands. Public options are visible to all sub-commands. 4. At least one sub-command!

warn

The crate is developed using Ubuntu 16.04, we can't assume that all platforms will work well. If you find that it can't work well in other platforms, please tell me.

contribute

Any useful contribute are welcome. You can send pull request to me.

License

GPL-3.0. Because open source is future.