#deserialize #serde #serde-json #visitor #multiple-type #this-or-that

serde-this-or-that

Custom deserialization for fields that can be specified as multiple types

8 releases

0.4.2 Feb 6, 2023
0.4.1 Feb 5, 2023
0.4.0 Apr 18, 2022
0.3.1 Apr 17, 2022
0.1.1 Apr 16, 2022

#234 in Encoding

Download history 1172/week @ 2023-12-13 1045/week @ 2023-12-20 616/week @ 2023-12-27 704/week @ 2024-01-03 1260/week @ 2024-01-10 1845/week @ 2024-01-17 1766/week @ 2024-01-24 1622/week @ 2024-01-31 1681/week @ 2024-02-07 1836/week @ 2024-02-14 1569/week @ 2024-02-21 1697/week @ 2024-02-28 2036/week @ 2024-03-06 2451/week @ 2024-03-13 1554/week @ 2024-03-20 2335/week @ 2024-03-27

8,688 downloads per month
Used in 11 crates (5 directly)

MIT license

26KB
322 lines

serde-this-or-that

github crates.io docs.rs build status

Custom deserialization for fields that can be specified as multiple types.


This crate works with Cargo with a Cargo.toml like:

[dependencies]
serde-this-or-that = "0.4"
serde = { version = "1", features = ["derive"] }
serde_json = "1"

Getting started

Add some usage to your application.

Here's an example of using serde-this-or-that in code:

use serde::Deserialize;
use serde_json::from_str;
use serde_this_or_that::{as_bool, as_f64, as_u64};

#[derive(Deserialize, Debug)]
#[serde(rename_all = "camelCase")]
struct MyStruct {
    #[serde(deserialize_with = "as_bool")]
    is_active: bool,
    #[serde(deserialize_with = "as_u64")]
    num_attempts: u64,
    #[serde(deserialize_with = "as_f64")]
    grade: f64,
}

fn main() -> Result<(), Box<dyn std::error::Error>> {
    let string = r#"
    {
        "isActive": "True",
        "numAttempts": "",
        "grade": "81"
    }
    "#;

    let s: MyStruct = from_str(string)?;
    println!("{s:#?}");

    assert!(s.is_active);
    assert_eq!(s.num_attempts, 0);
    assert_eq!(s.grade, 81.0);

    Ok(())
}

Exported Functions

Examples

You can check out sample usage of this crate in the examples/ folder in the project repo on GitHub.

Performance

The benchmarks suggest that implementing a custom Visitor as serde-this-or-that does, performs on average about 15x better than an approach with an untagged enum.

A separate benchmark compares performance against the serde_with crate: it indicates both crates perform about the same, assuming only DisplayFromStr is used. But when PickFirst is involved, serde-this-or-that appears to perform about 12x better in an average case.

The benchmarks live in the benches/ folder, and can be run with cargo bench.

Contributing

Contributions are welcome! Open a pull request to fix a bug, or open an issue to discuss a new feature or change.

Check out the Contributing section in the docs for more info.

License

This project is proudly licensed under the MIT license (LICENSE or http://opensource.org/licenses/MIT).

serde-this-or-that can be distributed according to the MIT license. Contributions will be accepted under the same license.

Authors

Dependencies

~110–355KB