-
|
Hello, is there a way I can create an operation and send it manually via reqwest as a multipart request? I have a mutation that uses graphql multipart request spec for file uploads, and I don't quite understand how I could do that. The field that requires it in my mutation: https://docs.saleor.io/docs/3.x/api-reference/miscellaneous/scalars/upload let category_create_operation: cynic::Operation<
gql_queries::CreateCategory,
gql_queries::CreateCategoryVariables,
> = gql_queries::CreateCategory::build(gql_queries::CreateCategoryVariables {
input: gql_queries::CategoryInput {
description: category_description,
name: Some(category_cp.name.as_str()),
slug: Some(category_cp.slug.as_str()),
seo: None,
background_image: None, //This is the Upload field
background_image_alt: Some(category_cp.name.as_str()),
metadata: Some(vec![MetadataInput {
key: "old_id",
value: &category_old_id,
}]),
private_metadata: None,
},
parent_id: category_parent_id,
});
let create_cat_response = client
.post(GQL_Endpoint)
.header("Authorization", &jwt)
.run_graphql(category_create_operation)
.await
.expect("Failed creating category");I also looked around for how to submit multipart mutations in general, but it's just not clicking in my head. Any tips appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
|
This isn't something the built in HTTP client integrations support, but that shouldn't prevent you from implementing it yourself.
I've never specifically done a multipart GraphQL request myself, but from skimming that article you linked I think you can probably create the GraphQL part with something like |
Beta Was this translation helpful? Give feedback.
-
|
This is rather difficult to solve... my API refuses the multipart query for some reason no matter what I try. {
"errors": [
{
"message": "Expecting value: line 1 column 1 (char 0)",
"extensions": {
"exception": {
"code": "GraphQLError",
"stacktrace": [
"graphql.error.base.GraphQLError: Expecting value: line 1 column 1 (char 0)"
]
}
}
}
]
}What I'm currently doing: pub fn main() {
let operation: Operation<MyMutation, MyMutationVariables> =
MyMutation::build(MyMutationVariables {
input: CategoryInput {
name: Some("Lol"),
seo: None,
slug: None,
metadata: None,
description: Some(Jsonstring {
0: "lol".to_string(),
}),
background_image: None,
private_metadata: None,
background_image_alt: None,
},
});
let file = std::fs::read("w.jpg").unwrap();
let file_part = Part::bytes(file)
.file_name("w.jpg")
.mime_str("image/jpeg")
.unwrap();
let map_part = Part::text(
serde_json::json!(
{
"1": [
"variables.input.backgroundImage"
]
}
)
.to_string(),
);
let gql_part = Part::text(serde_json::to_string(&operation).unwrap());
let form = Form::new()
.part("operations", gql_part)
.part("map", map_part)
.part("1", file_part);
// And finally, send the form
let client = reqwest::blocking::Client::new();
let mut req = client
.post("http://localhost:8000/graphql/")
//.post("http://localhost:3000")
.multipart(form)
.send()
.unwrap();
//std::fs::write("out.txt", req.text().unwrap()).unwrap();
dbg!(req.text().unwrap());
}And comparing the differences between a working one (done from dashboard of e-shop) and mine, I don't see why it's failing. After removing all the irrelevant headers, the difference is only a few headers and the queries themselves(Tho result of these queries should be the same) Saleor dashdoard successfull packets: The operation themselves are both styled the same too(top is Dashboard, bottom is mine): {
"operationName": "CategoryUpdate",
"variables": {
"id": "Q2F0ZWdvcnk6MQ==",
"input": { "backgroundImage": null }
},
"query": "mutation CategoryUpdate($id: ID!, $input: CategoryInput!) {\n categoryUpdate(id: $id, input: $input) {\n category {\n ...CategoryDetails\n __typename\n }\n errors {\n ...ProductError\n __typename\n }\n __typename\n }\n}\n\nfragment CategoryDetails on Category {\n id\n ...Metadata\n backgroundImage {\n alt\n url\n __typename\n }\n name\n slug\n description\n seoDescription\n seoTitle\n parent {\n id\n __typename\n }\n __typename\n}\n\nfragment Metadata on ObjectWithMetadata {\n metadata {\n ...MetadataItem\n __typename\n }\n privateMetadata {\n ...MetadataItem\n __typename\n }\n __typename\n}\n\nfragment MetadataItem on MetadataItem {\n key\n value\n __typename\n}\n\nfragment ProductError on ProductError {\n code\n field\n message\n __typename\n}\n"
},
{
"operationName": "MyMutation",
"variables": {
"input": {
"description": "lol",
"name": "Lol",
"slug": null,
"seo": null,
"backgroundImage": null,
"backgroundImageAlt": null,
"metadata": null,
"privateMetadata": null
}
},
"query": "mutation MyMutation($input: CategoryInput!) {\n categoryCreate(input: $input) {\n errors {\n message\n code\n field\n values\n }\n category {\n id\n }\n }\n}\n\n"
} |
Beta Was this translation helpful? Give feedback.
-
|
That error looks a lot like a JSON decoding error. If you look at the docs for CategoryInput You probably want to make it valid JSON, I think that will fix your issue. I see you're doing this: So I assume you've defined something like A slightly better (but definitely more effort) solution might be to change that struct to Up to you which path you want to go down. |
Beta Was this translation helpful? Give feedback.
-
|
@obmarg Thank you so much for taking the time to look at it, you are absolutely correct. Setting that field to None returns permission issues(forgot to include auth token), meaning the jsonstring was the issue. I will see how to add that functionality. I will also write saleor about the error message not being good, cause it should've said which field caused the error, but it instead made me think the whole query was invalid. Thanks again so much <3 |
Beta Was this translation helpful? Give feedback.
-
|
for future readers, the result can then be parsed from the response text as such: let result: GraphQlResponse<MyMutation> = serde_json::from_str(&req.text().await?)?; |
Beta Was this translation helpful? Give feedback.
-
|
I assume this is let result: GraphQlResponse<MyMutation> = &req.json().await?; |
Beta Was this translation helpful? Give feedback.
That error looks a lot like a JSON decoding error.
If you look at the docs for CategoryInput
descriptionis a JSONString, which I assume should be a string containing JSON. You can see from your request dump thatdescriptionis being set to"lol"which isn't valid JSON.You probably want to make it valid JSON, I think that will fix your issue.
I see you're doing this:
So I assume you've defined something like
struct Jsonstring(String). You could either useserde_json::to_stringto populate that string with JSON, or hardcode the JSON by hand.A slightly better (but definitely more effort) solution…