Crates.io | slog_derive |
lib.rs | slog_derive |
version | 0.2.0 |
source | src |
created_at | 2018-02-14 12:42:52.767 |
updated_at | 2019-10-12 08:16:36.247087 |
description | Custom derives for use with slog. |
homepage | |
repository | https://github.com/slog-rs/derive |
max_upload_size | |
id | 51133 |
size | 15,088 |
Custom derives for use with slog logging.
KV
DeriveSometimes you'll want to log the struct's contents in your application, for example when you've just started and want to record the configuration details for debugging purposes. Usually you'd need to do something like this:
#[macro_use]
extern crate slog;
use std::path::PathBuf;
struct Config {
width: f64,
height: f64,
url: String,
}
let cfg = Config { ... };
debug!(logger, "Loaded Config";
"width" => cfg.width,
"height" => cfg.height,
"url" => cfg.url);
# }
This is where the KV
trait comes in. Implementing it lets you log a type
as a bunch of key-value pairs, translating the previous log statement into
something like this:
debug!(logger, "Loaded Config"; cfg);
This crate provides a custom derive which will implement KV
for you.
It'll just iterate over each field in your struct
and invoke
Value::serialize()
on each. You can also use the #[slog(skip)]
attribute
to skip specific fields.
#[derive(KV)]
pub struct Config {
width: f64,
height: f64,
#[slog(skip)]
url: String,
}
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.