The buildSchema function takes a schema in SDL (schema definition language) and returns a GraphQLSchema object. Given two identical schemas generated with each method, runtime performance would be the same. Startup time for a server using buildSchema would be slower since parsing the SDL adds an extra step that would not otherwise exist — whether … Read more
I’ve come up with a middle-ground solution. Rather than trying to push this complexity onto GraphQL, I’m opting to just use the String type and JSON.stringifying my data before setting it on the field. So everything gets stringified, and later in my application when I need to consume this field, I JSON.parse the result to … Read more
Post request needs to manage headers info. Using Http client – Content-Type: application/json Using Postman client – Content-Type: application/graphql but request body looks like string {“query”:”mutation{update(id:1,x1:\”zazaz\”,x2:\”zazaz\”……){id x1 x2}}”}
The Node root field, in combination with globally unique IDs, comes into play when Relay needs to refetch an object. Refetching occurs when you call this.props.relay.forceFetch() or when you add fields to the query for an object whose global ID is known because it has already been partially fetched. In cases like these, Relay will … Read more
In the GraphQL spec, objects and input objects are distinct things. Quoting the spec for input objects: Fields can define arguments that the client passes up with the query, to configure their behavior. These inputs can be Strings or Enums, but they sometimes need to be more complex than this. The Object type… is inappropriate … Read more
You can definitely query with an array of values! Here’s what the query itself would look like: { events(containsId: [1,2,3]) { … } } And the type would look something like: const eventsType = new GraphQLObjectType({ name: ‘events’, type: // your type definition for events, args: { containsId: new GraphQLList(GraphQLID) }, … }); If you … Read more
As of the time of writing, there isn’t a built-in feature in GraphQL-JS or Apollo Server to handle this concern, but it’s something that should definitely have a simple solution as GraphQL becomes more popular. This concern can be addressed with several approaches at several levels of the stack, and should also always be combined … Read more
Non-null means exactly what it sounds like — not null. An empty array is not null — it’s still returning a value. Here is a summary table: declaration accepts: | null | [] | [null] | [{foo: ‘BAR’}] ———————————————————————— [Vote!]! | no | yes | no | yes [Vote]! | no | yes | yes … Read more
It looks like the grammar allows default values on input object types, so you can declare input ExampleInput { value: Int = 0 another: String isAvailable: Boolean = false } The spec is clear that default values exist and explains how they get used (first bullet under “Input Coercion”). (Whether any specific tooling supports this … Read more
From the docs: A GraphQL object type has a name and fields, but at some point those fields have to resolve to some concrete data. That’s where the scalar types come in: they represent the leaves of the query. GraphQL requires that you construct your queries in a way that only returns concrete data. Each … Read more