3 unstable releases

0.2.0 Oct 12, 2019
0.1.1 Oct 22, 2018
0.1.0 Feb 14, 2018

#613 in Debugging

Download history 2338/week @ 2023-12-23 3504/week @ 2023-12-30 5041/week @ 2024-01-06 5274/week @ 2024-01-13 5345/week @ 2024-01-20 5573/week @ 2024-01-27 6395/week @ 2024-02-03 6152/week @ 2024-02-10 8165/week @ 2024-02-17 8101/week @ 2024-02-24 7940/week @ 2024-03-02 9019/week @ 2024-03-09 9051/week @ 2024-03-16 8580/week @ 2024-03-23 8732/week @ 2024-03-30 5707/week @ 2024-04-06

33,531 downloads per month
Used in 6 crates (4 directly)

MIT/Apache

14KB
132 lines

Slog Derives

Build Status Crates.io Link Online Documentation

Custom derives for use with slog logging.

The KV Derive

Sometimes 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,
}

License

Licensed under either of

at your option.

Contribution

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.

Dependencies

~1.5MB
~33K SLoC