mutation CreateMovie ($title: String!, $launched: Date!) {
createMovie (title: $title, launched: $launched){
id
title
launched
}
}
[submitted data]
{
“title”: “Seven Samurai”
“launched”: “1950”
}
All queries, together with mutation queries, can return knowledge. Right here, the listing of fields within the curly braces after createMovie specifies what we need to see returned from the server after a brand new document is created with this request. The worth for the id discipline, on this case, could be created by the database; the values for the opposite fields are submitted within the question.
One other factor to remember is that the queries and knowledge varieties used to return knowledge are by design totally different from these used to request knowledge. Mutation queries must validate incoming knowledge, so the kinds used for these queries are supposed to serve that perform. Likewise, the fields utilized in returned question objects are for show, not validation. For those who absorb a GraphQL object as returned from a question, it may need fields with round references or different points that make it unusable as a question parameter.
Why use GraphQL?
A key motive to select GraphQL over REST is the express, declarative nature of GraphQL queries. Having a proper definition for a way queries and returned knowledge ought to look has benefits other than being constant throughout APIs and implementations.
