4 releases

0.0.4 Aug 1, 2024
0.0.3 Jul 31, 2024
0.0.2 Jul 31, 2024
0.0.1 Jul 31, 2024

#1639 in Parser implementations

Download history 270/week @ 2024-07-29 14/week @ 2024-08-05 8/week @ 2024-09-16 22/week @ 2024-09-30 1/week @ 2024-10-07

96 downloads per month

BSD-2-Clause

23KB
458 lines

serde-double-tag

This crates provides derive macros for a double tagged enum representation for serde. It is basically a combination of externally and adjecently tagged enums.

If you enable the schemars feature, the crate also exposes a derive macro for the schemars::JsonSchema trait.

For example, consider this enum:

#[derive(serde_double_tag::Deserialize, serde_double_tag::Serialize)]
#[serde(tag = "species")]
#[serde(rename_all = "snake_case")]
enum Friend {
  Human {
    name: String,
    hobbies: Vec<String>,
  },
  Dog {
    name: String,
    color: String,
  }
}

A Friend::Human will be serialized as:

{
  "species": "human",
  "human": {
    "name": "Zohan",
    "hobbies": ["hair dressing"],
  }
}

Similarly, a Friend::Dog will be serialized as:

{
  "species": "dog",
  "dog": {
    "name": "Scrappy",
    "color": "white and gray",
  }
}

This enum representation could be useful if you want data for the different variants to co-exist in a single file or in your database. Since each variant uses a different field name, they will never conflict. And since there is still a separate field for the enum tag, you can still known which variant is actually active.

Currently supported serde attributes:

  • `#[serde(rename = "...")]
  • `#[serde(rename_all = "...")]
  • `#[serde(rename_all_fields = "...")]
  • `#[serde(deny_unknown_fields = "...")]

Dependencies

~0.3–1.2MB
~27K SLoC