serde

I have datatypes which look like this: #[derive(Serialize, Deserialize, Debug)] #[serde(rename_all = "camelCase")] pub struct Matrix { #[serde(rename = "numColumns")] pub num_cols: usize, #[serde(rename = "numRows")] pub num_rows: usize, pub data: Vec<f64>, } My JSON bodies look something like this: { "numRows": 2, "numColumns": 1, "data": [1.0, "NaN"] } This is the serialization provided by Jackson (from a Java server we use), and is valid JSON. Unfortunately if we call serde_json::from_str(&blob) we get an error: Error("invalid type: string "NaN", expected f64", [snip] I understand there are

Using the serde_json crate, I can use ::serde_json::to_string(&obj) to serialize an object into a JSON string. The resulting JSON uses compact formatting, like: {"foo":1,"bar":2} But how do I generate pretty/indented JSON? For example, I'd like to get this: { "foo": 1, "bar": 2 } The serde_json::to_string_pretty function generates pretty-printed indented JSON. #[macro_use] extern crate serde_json; fn main() { let obj = json!({"foo":1,"bar":2}); println!("{}", serde_json::to_string_pretty(&obj).unwrap()); } This approach defaults to 2 spaces of indentation, which happens to be what you asked

I have a tree of serde-annotated structs and it succeeds in parsing the sample XML, including this fragment: <bmsg> <cmsg> <!-- ... --> <cmsg> <bmsg> Now I am testing with a large sample XML file and the following structs fail because sometimes <cmsg>..</cmsg> is missing. I was deserializing this using: #[derive(Serialize,Deserialize, Debug)] struct A { #[serde(rename="bmsg")] messages: B, // <==== } #[derive(Serialize,Deserialize, Debug)] struct B { // bmsg #[serde(rename="cmsg")] list: Vec<C>, } Which resulted in an error in the second struct: panicked at 'called `Result::unwrap()` on an

I'm relatively new to Rust, and even more so to Serde, so I'm having trouble finding out if this is even doable. I have a JSON file which has two different representations for the same key: "coordinates": [ [ [ 121.423364, 24.9913596 ], [ 121.4233327, 24.9912977 ], ] ] and this: "coordinates": [ [ 121.4472492, 25.0052053 ], [ 121.4466457, 25.0028547 ] ] There is a two dimensional array and a three dimensional array representing ways in the same attribute. This makes the file hard to serialize. Here is the code that I implemented: #[derive(Serialize, Deserialize, Debug)] struct Geometry { #

My code: fn request_add<T>(request: &mut Request, collection_name: &'static str) -> Fallible<Fallible<String>> where T: serde::Serialize + serde::de::DeserializeOwned, { let add_dao = dao::MongoDao::new(collection_name); let obj = serde_json::from_reader::<Body, T>(request.body)?; //cannot move out of borrowed content Ok(add_dao.add(&obj)) } I have a cannot move out of borrowed content error, because request is a reference, but why does serde_json::from_reader not use a mut reference? Why does it need ownership? And how can I fix it? Because it's an API guideline : Generic reader/writer