You can simply use a Vec: use serde::{Serialize, Deserialize}; #[derive(Serialize, Deserialize, Debug)] struct Foo { data: String, } fn main() -> Result<(), serde_json::Error> { let data = r#”[ { “data”: “value1” }, { “data”: “value2” }, { “data”: “value3” } ]”#; let datas: Vec<Foo> = serde_json::from_str(data)?; for data in datas.iter() { println!(“{:#?}”, data); } Ok(()) … Read more
The serialize_with attribute You can use the serialize_with attribute to provide a custom serialization function for your field: use serde::{Serialize, Serializer}; // 1.0.104 fn round_serialize<S>(x: &f32, s: S) -> Result<S::Ok, S::Error> where S: Serializer, { s.serialize_f32(x.round()) } #[derive(Debug, Serialize)] pub struct NodeLocation { #[serde(rename = “nodeId”)] id: u32, #[serde(serialize_with = “round_serialize”)] lat: f32, #[serde(serialize_with = … Read more
I found an answer from Serde issue 891: I should use DeserializeOwned instead of Deserialize.
The deserialize_with attribute The easiest solution is to use the Serde field attribute deserialize_with to set a custom serialization function for your field. You then can get the raw string and convert it as appropriate: use serde::{de::Error, Deserialize, Deserializer}; // 1.0.94 use serde_json; // 1.0.40 #[derive(Debug, Deserialize)] struct EtheriumTransaction { #[serde(deserialize_with = “from_hex”)] account: u64, … Read more
The general problem is that the code has multiple versions of the crate, each providing a different version of the traits. The fact that Rust allows this is a good thing, but the error messages around it are confusing. Your crate implements Serialize from version A but the library is using version B in a … Read more