4 releases

0.2.2 Sep 6, 2024
0.2.1 May 1, 2024
0.2.0 May 1, 2024
0.1.0 Jan 19, 2024

#115 in Configuration

Download history 6686/week @ 2024-08-18 5882/week @ 2024-08-25 7346/week @ 2024-09-01 5737/week @ 2024-09-08 3823/week @ 2024-09-15 7053/week @ 2024-09-22 6225/week @ 2024-09-29 7099/week @ 2024-10-06 8559/week @ 2024-10-13 8800/week @ 2024-10-20 7307/week @ 2024-10-27 7923/week @ 2024-11-03 4435/week @ 2024-11-10 7387/week @ 2024-11-17 10157/week @ 2024-11-24 12319/week @ 2024-12-01

34,755 downloads per month

MIT/Apache

29KB
298 lines

clap-adapters

Adapter types for declaratively loading configurations with clap

Did you know that any type that implements FromStr can be used in a clap derive struct? That means that any logic you can fit into a fn(&str) -> Result<T, Error> can be run at parsing-time. This can be expecially useful for declaratively selecting config files or doing other cool stuff. Check this out:

use clap::Parser;
use clap_adapters::prelude::*;

#[derive(Debug, Parser)]
struct Cli {
    /// Path to a config file of arbitrary Json
    #[clap(long)]
    config: PathTo<JsonOf<serde_json::Value>>,
}

fn main() {
    // Create a config file in a temporary directory
    let config_dir = tempfile::tempdir()?;
    let config_path = config_dir.path().join("config.json");
    let config_path_string = config_path.display().to_string();

    // Write a test config of {"hello":"world"} to the config file
    let config = serde_json::json!({"hello": "world"});
    let config_string = serde_json::to_string(&config)?;
    std::fs::write(&config_path, &config_string)?;

    // Parse our CLI, passing our config file path to --config
    let cli = Cli::parse_from(["app", "--config", &config_path_string]);
    let data = cli.config.data();

    // We should expect the value we get to match what we wrote to the config
    assert_eq!(data, &serde_json::json!({"hello":"world"}));
}

Extending clap-adapters

You can implement additional composable adapters by defining new types that implement traits in this crate. For example, by implementing FromReader, you could define an adapter that can construct itself from a file path, nesting your adapter into PathTo<T>, like PathTo<YourAdapter>.

Dependencies

~4–16MB
~161K SLoC