Mixing
Deserialization of JSON reponse keeps quotation marks in Strings
I am querying a Google API using reqwest:
let request_url = format!(
"https://maps.googleapis.com/maps/api/place/findplacefromtext/json?input=*
&inputtype=textquery
&fields=formatted_address,name,place_id,types
&locationbias=circle:50@{},{}
&key=my-secret-key",
lat, lng
);
let mut response = reqwest::get(&request_url).expect("pffff");
let gr: GoogleResponse = response.json::<GoogleResponse>().expect("geeez");
The GoogleResponse struct is defined as
#[derive(Debug, Serialize, Deserialize)]
pub struct DebugLog {
pub line: Vec<String>,
}
#[derive(Debug, Serialize, Deserialize)]
pub struct Candidate {
pub formatted_address: String,
pub name: String,
pub place_id: String,
pub types: Vec<String>,
}
#[derive(Debug, Serialize, Deserialize)]
pub struct GoogleResponse {
pub candidates: Vec<Candidate>,
pub debug_log: DebugLog,
pub status: String,
}
This all compiles and I can make the request, however the result that I am having in the String fields contain the original ". Is it supposed to be this way?
For instance, when printing one of the formatted addresses I get:
"result": ""Street blabh blahab blahb"",
When I really wanted just
"result": "Street blabh blahab blahb",
Am I doing something wrong or is this expected behavior?
json serialization rust serde rust-rocket
edited Dec 4 '18 at 21:27
Shepmaster
148k12285419
asked Nov 19 '18 at 16:20
LudeeD
317
add a comment |
I am querying a Google API using reqwest:
let request_url = format!(
"https://maps.googleapis.com/maps/api/place/findplacefromtext/json?input=*
&inputtype=textquery
&fields=formatted_address,name,place_id,types
&locationbias=circle:50@{},{}
&key=my-secret-key",
lat, lng
);
let mut response = reqwest::get(&request_url).expect("pffff");
let gr: GoogleResponse = response.json::<GoogleResponse>().expect("geeez");
The GoogleResponse struct is defined as
#[derive(Debug, Serialize, Deserialize)]
pub struct DebugLog {
pub line: Vec<String>,
}
#[derive(Debug, Serialize, Deserialize)]
pub struct Candidate {
pub formatted_address: String,
pub name: String,
pub place_id: String,
pub types: Vec<String>,
}
#[derive(Debug, Serialize, Deserialize)]
pub struct GoogleResponse {
pub candidates: Vec<Candidate>,
pub debug_log: DebugLog,
pub status: String,
}
This all compiles and I can make the request, however the result that I am having in the String fields contain the original ". Is it supposed to be this way?
For instance, when printing one of the formatted addresses I get:
"result": ""Street blabh blahab blahb"",
When I really wanted just
"result": "Street blabh blahab blahb",
Am I doing something wrong or is this expected behavior?
json serialization rust serde rust-rocket
edited Dec 4 '18 at 21:27
Shepmaster
148k12285419
asked Nov 19 '18 at 16:20
LudeeD
317
2
In the future, please provide a proper MCVE, where you descripe your problem in a minimal way and let us see some code please.
– hellow
Nov 19 '18 at 16:26
add a comment |
I am querying a Google API using reqwest:
let request_url = format!(
"https://maps.googleapis.com/maps/api/place/findplacefromtext/json?input=*
&inputtype=textquery
&fields=formatted_address,name,place_id,types
&locationbias=circle:50@{},{}
&key=my-secret-key",
lat, lng
);
let mut response = reqwest::get(&request_url).expect("pffff");
let gr: GoogleResponse = response.json::<GoogleResponse>().expect("geeez");
The GoogleResponse struct is defined as
#[derive(Debug, Serialize, Deserialize)]
pub struct DebugLog {
pub line: Vec<String>,
}
#[derive(Debug, Serialize, Deserialize)]
pub struct Candidate {
pub formatted_address: String,
pub name: String,
pub place_id: String,
pub types: Vec<String>,
}
#[derive(Debug, Serialize, Deserialize)]
pub struct GoogleResponse {
pub candidates: Vec<Candidate>,
pub debug_log: DebugLog,
pub status: String,
}
This all compiles and I can make the request, however the result that I am having in the String fields contain the original ". Is it supposed to be this way?
For instance, when printing one of the formatted addresses I get:
"result": ""Street blabh blahab blahb"",
When I really wanted just
"result": "Street blabh blahab blahb",
Am I doing something wrong or is this expected behavior?
json serialization rust serde rust-rocket
edited Dec 4 '18 at 21:27
Shepmaster
148k12285419
asked Nov 19 '18 at 16:20
LudeeD
317
I am querying a Google API using reqwest:
let request_url = format!(
"https://maps.googleapis.com/maps/api/place/findplacefromtext/json?input=*
&inputtype=textquery
&fields=formatted_address,name,place_id,types
&locationbias=circle:50@{},{}
&key=my-secret-key",
lat, lng
);
let mut response = reqwest::get(&request_url).expect("pffff");
let gr: GoogleResponse = response.json::<GoogleResponse>().expect("geeez");
The GoogleResponse struct is defined as
#[derive(Debug, Serialize, Deserialize)]
pub struct DebugLog {
pub line: Vec<String>,
}
#[derive(Debug, Serialize, Deserialize)]
pub struct Candidate {
pub formatted_address: String,
pub name: String,
pub place_id: String,
pub types: Vec<String>,
}
#[derive(Debug, Serialize, Deserialize)]
pub struct GoogleResponse {
pub candidates: Vec<Candidate>,
pub debug_log: DebugLog,
pub status: String,
}
This all compiles and I can make the request, however the result that I am having in the String fields contain the original ". Is it supposed to be this way?
For instance, when printing one of the formatted addresses I get:
"result": ""Street blabh blahab blahb"",
When I really wanted just
"result": "Street blabh blahab blahb",
Am I doing something wrong or is this expected behavior?
json serialization rust serde rust-rocket
json serialization rust serde rust-rocket
edited Dec 4 '18 at 21:27
Shepmaster
148k12285419
asked Nov 19 '18 at 16:20
LudeeD
317
edited Dec 4 '18 at 21:27
Shepmaster
148k12285419
asked Nov 19 '18 at 16:20
LudeeD
317
edited Dec 4 '18 at 21:27
Shepmaster
148k12285419
edited Dec 4 '18 at 21:27
Shepmaster
148k12285419
edited Dec 4 '18 at 21:27
Shepmaster
148k12285419
148k12285419
asked Nov 19 '18 at 16:20
LudeeD
317
asked Nov 19 '18 at 16:20
LudeeD
317
asked Nov 19 '18 at 16:20
LudeeD
317
317
2
In the future, please provide a proper MCVE, where you descripe your problem in a minimal way and let us see some code please.
– hellow
Nov 19 '18 at 16:26
add a comment |
2
In the future, please provide a proper MCVE, where you descripe your problem in a minimal way and let us see some code please.
– hellow
Nov 19 '18 at 16:26
2
2
In the future, please provide a proper MCVE, where you descripe your problem in a minimal way and let us see some code please.
– hellow
Nov 19 '18 at 16:26
In the future, please provide a proper MCVE, where you descripe your problem in a minimal way and let us see some code please.
– hellow
Nov 19 '18 at 16:26
add a comment |
1 Answer
1
active
oldest
votes
I'll try to provide a simple example here.
extern crate serde; // 1.0.80
extern crate serde_json; // 1.0.33
use serde_json::Value;
const JSON: &str = r#"{
"name": "John Doe",
"age": 43
}"#;
fn main() {
let v: Value = serde_json::from_str(JSON).unwrap();
println!("{} is {} years old", v["name"], v["age"]);
}
(playground)
will lead to
"John Doe" is 43 years old
The reason is, that v["name"] is not a String, but a Value instead (You can check that by adding the line let a: () = v["name"]; which will result in the error: expected (), found enum 'serde_json::Value').
If you want a &str/String, you have to convert it first by using Value::as_str.
If you change the println! line accordingly:
println!("{} is {} years old", v["name"].as_str().unwrap(), v["age"]);
it will print out:
John Doe is 43 years old
answered Nov 19 '18 at 16:31
hellow
4,79532042
Thanks, that really helped
– LudeeD
Nov 19 '18 at 16:40
This answer makes no sense to me in relation to the original question — the OP never uses the indexing syntax. They specifically use typed deserialization.
– Shepmaster
Nov 19 '18 at 17:35
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53378780%2fdeserialization-of-json-reponse-keeps-quotation-marks-in-strings%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I'll try to provide a simple example here.
extern crate serde; // 1.0.80
extern crate serde_json; // 1.0.33
use serde_json::Value;
const JSON: &str = r#"{
"name": "John Doe",
"age": 43
}"#;
fn main() {
let v: Value = serde_json::from_str(JSON).unwrap();
println!("{} is {} years old", v["name"], v["age"]);
}
(playground)
will lead to
"John Doe" is 43 years old
The reason is, that v["name"] is not a String, but a Value instead (You can check that by adding the line let a: () = v["name"]; which will result in the error: expected (), found enum 'serde_json::Value').
If you want a &str/String, you have to convert it first by using Value::as_str.
If you change the println! line accordingly:
println!("{} is {} years old", v["name"].as_str().unwrap(), v["age"]);
it will print out:
John Doe is 43 years old
answered Nov 19 '18 at 16:31
hellow
4,79532042
Thanks, that really helped
– LudeeD
Nov 19 '18 at 16:40
This answer makes no sense to me in relation to the original question — the OP never uses the indexing syntax. They specifically use typed deserialization.
– Shepmaster
Nov 19 '18 at 17:35
add a comment |
I'll try to provide a simple example here.
extern crate serde; // 1.0.80
extern crate serde_json; // 1.0.33
use serde_json::Value;
const JSON: &str = r#"{
"name": "John Doe",
"age": 43
}"#;
fn main() {
let v: Value = serde_json::from_str(JSON).unwrap();
println!("{} is {} years old", v["name"], v["age"]);
}
(playground)
will lead to
"John Doe" is 43 years old
The reason is, that v["name"] is not a String, but a Value instead (You can check that by adding the line let a: () = v["name"]; which will result in the error: expected (), found enum 'serde_json::Value').
If you want a &str/String, you have to convert it first by using Value::as_str.
If you change the println! line accordingly:
println!("{} is {} years old", v["name"].as_str().unwrap(), v["age"]);
it will print out:
John Doe is 43 years old
answered Nov 19 '18 at 16:31
hellow
4,79532042
Thanks, that really helped
– LudeeD
Nov 19 '18 at 16:40
This answer makes no sense to me in relation to the original question — the OP never uses the indexing syntax. They specifically use typed deserialization.
– Shepmaster
Nov 19 '18 at 17:35
add a comment |
I'll try to provide a simple example here.
extern crate serde; // 1.0.80
extern crate serde_json; // 1.0.33
use serde_json::Value;
const JSON: &str = r#"{
"name": "John Doe",
"age": 43
}"#;
fn main() {
let v: Value = serde_json::from_str(JSON).unwrap();
println!("{} is {} years old", v["name"], v["age"]);
}
(playground)
will lead to
"John Doe" is 43 years old
The reason is, that v["name"] is not a String, but a Value instead (You can check that by adding the line let a: () = v["name"]; which will result in the error: expected (), found enum 'serde_json::Value').
If you want a &str/String, you have to convert it first by using Value::as_str.
If you change the println! line accordingly:
println!("{} is {} years old", v["name"].as_str().unwrap(), v["age"]);
it will print out:
John Doe is 43 years old
answered Nov 19 '18 at 16:31
hellow
4,79532042
I'll try to provide a simple example here.
extern crate serde; // 1.0.80
extern crate serde_json; // 1.0.33
use serde_json::Value;
const JSON: &str = r#"{
"name": "John Doe",
"age": 43
}"#;
fn main() {
let v: Value = serde_json::from_str(JSON).unwrap();
println!("{} is {} years old", v["name"], v["age"]);
}
(playground)
will lead to
"John Doe" is 43 years old
The reason is, that v["name"] is not a String, but a Value instead (You can check that by adding the line let a: () = v["name"]; which will result in the error: expected (), found enum 'serde_json::Value').
If you want a &str/String, you have to convert it first by using Value::as_str.
If you change the println! line accordingly:
println!("{} is {} years old", v["name"].as_str().unwrap(), v["age"]);
it will print out:
John Doe is 43 years old
answered Nov 19 '18 at 16:31
hellow
4,79532042
edited Nov 19 '18 at 16:37
answered Nov 19 '18 at 16:31
hellow
4,79532042
answered Nov 19 '18 at 16:31
hellow
4,79532042
answered Nov 19 '18 at 16:31
hellow
4,79532042
4,79532042
Thanks, that really helped
– LudeeD
Nov 19 '18 at 16:40
This answer makes no sense to me in relation to the original question — the OP never uses the indexing syntax. They specifically use typed deserialization.
– Shepmaster
Nov 19 '18 at 17:35
add a comment |
Thanks, that really helped
– LudeeD
Nov 19 '18 at 16:40
This answer makes no sense to me in relation to the original question — the OP never uses the indexing syntax. They specifically use typed deserialization.
– Shepmaster
Nov 19 '18 at 17:35
Thanks, that really helped
– LudeeD
Nov 19 '18 at 16:40
Thanks, that really helped
– LudeeD
Nov 19 '18 at 16:40
This answer makes no sense to me in relation to the original question — the OP never uses the indexing syntax. They specifically use typed deserialization.
– Shepmaster
Nov 19 '18 at 17:35
This answer makes no sense to me in relation to the original question — the OP never uses the indexing syntax. They specifically use typed deserialization.
– Shepmaster
Nov 19 '18 at 17:35
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53378780%2fdeserialization-of-json-reponse-keeps-quotation-marks-in-strings%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
In the future, please provide a proper MCVE, where you descripe your problem in a minimal way and let us see some code please.
– hellow
Nov 19 '18 at 16:26