6 releases (3 breaking)
0.4.1 | Jul 10, 2024 |
---|---|
0.4.0 | Oct 11, 2023 |
0.3.0 | Oct 9, 2023 |
0.2.0 | Sep 24, 2023 |
0.1.0 | May 13, 2023 |
#451 in Rust patterns
288 downloads per month
Used in rs_envflag_macros
9KB
50 lines
rs_envflag
This crate provides an easy to define flags controlled by environment variables. It is a rust, and of course much more rustacean, reimplementation of https://github.com/TimeExceed/envflag.
a str flag without default values
Here is an example about defining a str flag.
use rs_envflag_macros::*;
/// an example about str flag
#[envflag]
const STR_FLAG: Option<String>;
fn main() {
if let Some(x) = STR_FLAG.fetch().unwrap() {
println!("{}", x);
} else {
println!("not present.");
}
}
When we run it directly, STR_FLAG
will be None
.
$ cargo build --examples && target/debug/examples/str
not present.
But once STR_FLAG
is set, it looks like
$ cargo build --examples && STR_FLAG=abc target/debug/examples/str
abc
a str flag with default values
Also we can define default values to flags.
use rs_envflag_macros::*;
/// an example about str flag with default
#[envflag(default="abc")]
const STR_FLAG_W_DEFAULT: String;
fn main() {
println!("{}", STR_FLAG_W_DEFAULT.fetch().unwrap());
}
Then we will compile and run it.
$ cargo build --examples && target/debug/examples/str && STR_FLAG_W_DEFAULT=xyz target/debug/examples/str
xyz
i64/f64/bool flags with/without default values
We can also define i64, f64 and bool flags, either with or without, default values. Please refer to examples/ for details.
customized types and customized parsers
Now we will show how to define flags with customized types.
use rs_envflag_macros::*;
#[envflag(parser=v_parser)]
const X: Option<V>;
fn main() {
if let Some(x) = X.fetch().unwrap() {
println!("{:?}", x);
} else {
println!("not present.");
}
}
#[derive(Debug)]
struct V(String);
fn v_parser(_key: &str, value: &str) -> anyhow::Result<V> {
Ok(V(value.to_string()))
}
- Just a parser is required. It must accept 2 arguments. The 2nd argument is the value to parse. The 1st is the name of the env variable. This is not necessary for parsing values. But it is convenient to log something about parsing errors and warnings.
To define default values of env flags of customized types, more things are required.
use rs_envflag_macros::*;
#[envflag(parser=v_parser, default=&V::DEFAULT)]
const X_W_DEFAULT: V;
fn main() {
println!("{:?}", X_W_DEFAULT.fetch().unwrap());
}
#[derive(Debug, Clone)]
struct V(String);
impl V {
const DEFAULT: V = V(String::new());
}
fn v_parser(_key: &str, value: &str) -> anyhow::Result<V> {
Ok(V(value.to_string()))
}
- Besides parsers, const default values are required.
And they must be refered by references, e.g., in this example
default=&V::DEFAULT
. V
must implement theClone
trait, so the default value will be cloned when necessary.
flag renaming
Names of env variables and those in rust can be different.
We support it by env_name
attribute.
use rs_envflag_macros::*;
/// env is named as `XYZ` rather `ABC`.
#[envflag(env_name="XYZ")]
const ABC: Option<String>;
fn main() {
if let Some(x) = ABC.fetch().unwrap() {
println!("{}", x);
} else {
println!("not present.");
}
}
Now, this program will response what env variable XYZ
is.
$ cargo build --examples && target/debug/examples/env_rename && XYZ=xyz target/debug/examples/env_rename
not present.
xyz
crate renaming
Occasionally, crate rs_envflag
have to be imported as a different name.
We also support this case by crate
attribute.
Please refer to examples/crate_rename.rs for details.
Dependencies
~135KB