According to this Github issue you cannot return nothing. You can define a return type which is nullable e.g. type Mutation { addElement(element: ElementData): ID removeElement(id: ID): Boolean } But I suggest you return the id of the deleted element, because if you want to work with a cached store you have to update the … Read more
There’s a better way to do it using the REST client Insomnia Docs are here, how to send graphql queries: https://support.insomnia.rest/article/61-graphql Below are the steps for postman Step 1. Run the GraphiQL in Chrome, open the Chrome Dev Console, click the Network tab, and make the query from graphiql, when you make the query, network … Read more
The serialize method would be called when the value of the type is going to be sent to the client as a response. Since the values on the output is in the form of JSON, the return value of serialize could be anything. Could be string, number, array, object … The other two methods (parseValue … Read more
That means that the field is non-nullable. See more info in Graphql – Schemas and Types
From the spec: The GraphQL Object type (ObjectTypeDefinition)… is inappropriate for re‐use [as an input], because Object types can contain fields that define arguments or contain references to interfaces and unions, neither of which is appropriate for use as an input argument. For this reason, input objects have a separate type in the system. That’s … Read more
I have viewed the Angular Air Episode 26: FalcorJS and Angular 2 where Jafar Husain answers how GraphQL compares to FalcorJS. This is the summary (paraphrasing): FalcorJS and GraphQL are tackling the same problem (querying data, managing data). The important distinction is that GraphQL is a query language and FalcorJS is not. When you are … Read more