In graphql-js resolvers expose a fourth argument called resolve info. This field contains more information about the field. From the GraphQL docs GraphQLObjectType config parameter type definition: // See below about resolver functions. type GraphQLFieldResolveFn = ( source?: any, args?: {[argName: string]: any}, context?: any, info?: GraphQLResolveInfo ) => any type GraphQLResolveInfo = { fieldName: … Read more
When requesting a field that resolves to an object type (or a list of an object type), you have to specify the fields on that object type as well. The list of fields for a particular field (or the root) is called a selection set or a sub selection and is wrapped by a pair … Read more
There’s two common reasons your field or fields are resolving to null: 1) returning data in the wrong shape inside your resolver; and 2) not using Promises correctly. Note: if you’re seeing the following error: Cannot return null for non-nullable field the underlying issue is that your field is returning null. You can still follow … Read more
Follow this https://github.com/facebook/graphql/issues/215, Graphql does not support scalar union types currently, you can do this union IntOrString = IntBox | StringBox type IntBox { value: Int } type StringBox { value: String } or you can have your custom type, see this graphql, union scalar type?
You can pass a variable to your query and use a Directive to fetch a field conditionally, like name @include(if: $shouldFetchName). See the docs for Directives.
As of September 2017, this is not possible. There is an ongoing discussion around this functionality.
GraphQL is two things: A query language A Type System When a GraphQL server receives a query to process it generally comes in as a single String. This string must be split into meaningful sub-strings (tokenization) and parsed into a representation that the machine understands. This representation is called an abstract syntax tree, or AST. … Read more
Yes, this is possible, but not in this form. GraphQL server will reject such query as a field with the same name used multiple times, but with different arguments. You need to use aliases: query { item1: myItem(size: 100, type: 2) { id, name } item2: myItem(size: 150, type: 2) { id, name } item3: … Read more
GraphQL relies on both the server and the client knowing ahead of time what fields are available available for each type. In some cases, the client can discover those fields (via introspection), but for the server, they always need to be known ahead of time. So to somehow dynamically generate those fields based on the … Read more
You have to add id also to the creator field: query getEvent($eventId: ID!) { Event(id:$eventId) { id headline photo location startTime creator { id username photo } } } In general, make sure to add id to all subselections of your queries.