graphql-js

When we are using graphqlHTTP, the first argument passed to the resolve method is actually the parameters passed by the client query not root this is fine for a query resolver. But for a usecase where field resolver needs to know of a value of the parent, how to achieve this? type Person { name: String, cityId: String, city: City, } In the above scenario I would like where city would be a field resolver, and it needs access to cityId which is a property on parent type. I assume this should have been passed as parameter to the field resolver but that is not the case. Is there a way to achieve

I was wondering if there's a way to share the common fields between Input and Type in GraphQL so that I don't have to define the same set of fields in multiple places. Example: input PersonInput { id: String! name: String address: String } type Person { id: String! name: String address: String } I know Fragment might be a solution, but if my understanding is correct, using Fragment always requires you to put an ON condition which makes it look like this: Fragment PersonCommonFields on Person { ... } There seems to be no way to specify "on Person/PersonInput". GraphQL fragments are for querying

I am using graphql-tools . After receiving a GraphQL query, I execute a search using ElasticSearch and return the data. However, usually the requested query includes only a few of the possible fields, not all. I want to pass only the requested fields to ElasticSearch. First, I need to get the requested fields. I can already get the whole query as a string. For example, in the resolver, const resolvers = { Query: { async user(p, args, context) { //can print query as following console.log(context.query) } ..... } } It prints as query User { user(id:"111") { id name address } } Is there any way

I started out with the relay-starter-kit and also worked my way through the Relay and GraphQL documentation. But there are quite a few areas that are unexplained and mysterious. Seriously I read a lot of documentations everywhere about all these things but couldn't find any satisfying explanations for the following questions: What is this for? I put logging but it never even gets called at all: var {nodeInterface, nodeField} = nodeDefinitions( (globalId) => { var {type, id} = fromGlobalId(globalId); if (type === 'User') { return getUser(id); } else if (type === 'Widget') { return getWidget(id)

Are there any notable differences between the two? Im interested in anything from runtime and startup performance to features and workflow differences. Documentation does a poor job on explaining the difference and when I should use one over the other. Example in both versions: buildSchema const { graphql, buildSchema } = require('graphql'); const schema = buildSchema(` type Query { hello: String } `); const root = { hello: () => 'Hello world!' }; graphql(schema, '{ hello }', root).then((response) => { console.log(response); }); GraphQLSchema const { graphql, GraphQLSchema, GraphQLObjectType,