New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
json serialization compatible problem #1121
Comments
Can not reproduce this on my end. Using the latest version of use serde::{Deserialize, Serialize};
#[derive(Serialize, Deserialize)]
struct Test {
sds: String
}
fn main() {
let test = Test { sds: "sds".to_string() };
let res = serde_json::to_string(&test).unwrap();
println!("{}", res);
} yields:
as expected, please provide more information and perhaps an simple example illustrating your issue. |
like let str = "sds";
let str_json = serde_json::to_string(str).unwrap();
println!("{:?}", str_json); // "\"sds\""
let res: Result<String, serde_json::Error> = serde_json::from_str(str);
println!("{:?}", res); // Err(Error("expected value", line: 1, column: 1)) |
is a valid json string. |
Oh, I guess you have confused "the string type in json" (i.e. the It's indeed better for |
I have a project that communicates with Java projects, and in some Java json parsing libraries, the String type is treated directly as
Now I receive a Java response that I must process before I can use serde_json
|
Such implementation would be incompatible with the JSON format specification, as both RFC 8259 and ECMA-404 define
Here is a simple JSON format verifier if you don't want to look into the specs (remember to uncheck the |
i know , so i hope have like a "Fix JSON" Feature, |
In that case, you probably should change your title to "Feature request: apply simple auto-corrections when deserialize", though I don't think that would be accepted. |
Deserializing things other than JSON is out of scope for this library. |
For example, in java interactions, fields of type String are serialized directly to sds instead of /"sds/", and using serde results in an error when serialization fails
expected value at line 1 column 1
Hopefully this is compatible
The text was updated successfully, but these errors were encountered: