serde-bool
Single value, true or false, boolean deserializers.
Examples
Supporting serde untagged enums where only one boolean value is valid, allowing fallthrough to the next variant. Avoids need to wrap all fields in Option<_> just in case feature is disabled.
#[derive(Debug, serde::Deserialize)]
struct Config {
feature: FeatureConfig,
}
#[derive(Debug, serde::Deserialize)]
#[serde(untagged)]
enum FeatureConfig {
Disabled {
enabled: serde_bool::False
},
Enabled {
#[serde(default)]
enabled: serde_bool::True,
key: String,
secret: String,
}
}
// disabled variant is matched
let config = toml::from_str::<Config>(r#"
[feature]
enabled = false
"#).unwrap();
assert!(matches!(config.feature, FeatureConfig::Disabled { .. }));
// if the type used `enabled: bool`, this would cause issues and require Option<_> wrappers plus
// further validation... instead an error is returned immediately regarding the missing fields
let config = toml::from_str::<Config>(r#"
[feature]
enabled = true
"#).unwrap_err();
// using a `#[serde(default)]` annotation makes `enabled = true` optional here
let config = toml::from_str::<Config>(r#"
[feature]
key = "foo"
secret = "bar"
"#).unwrap();
assert!(matches!(config.feature, FeatureConfig::Enabled { .. }));
// extra keys can exists in the disabled case, but as usual will not be captured
let config = toml::from_str::<Config>(r#"
[feature]
enabled = false
key = "foo"
secret = "bar"
"#).unwrap();
assert!(matches!(config.feature, FeatureConfig::Disabled { .. }));
298 Dec 28, 2022
2 Oct 24, 2022
36 May 8, 2023
3 Aug 21, 2023
3 Oct 23, 2023
26 Feb 7, 2022
2 Dec 21, 2021
7 Feb 7, 2023
35 Jun 26, 2022
196 Jan 2, 2023
92 Jan 3, 2023
8 Dec 3, 2022
175 Dec 31, 2022
4 Aug 14, 2022
94 Sep 29, 2022
0 Sep 4, 2022
9 Sep 12, 2022
30 Nov 25, 2022
44 Dec 4, 2022
2 Oct 24, 2022
2 Dec 21, 2021
9 Dec 7, 2022
2 Jun 7, 2022
17 Dec 31, 2022
44 Jan 20, 2023
5 Oct 24, 2023
4 Oct 30, 2023