Resolver chains in GraphQL - Step-by-Step Execution

Concept Flow - Resolver chains

Client sends query

↓

GraphQL Server parses query

↓

Root Resolver called

↓

Calls next resolver in chain

↓

Each resolver processes data

↓

Data returned up the chain

↓

Final response sent to client

Resolver chains process a GraphQL query step-by-step, where each resolver calls the next to fetch or compute data, passing results back up to form the final response.

Execution Sample

GraphQL

query {
  user(id: "1") {
    name
    posts {
      title
    }
  }
}

This query asks for a user's name and the titles of their posts, triggering a chain of resolvers.

Execution Table

Step	Resolver Called	Input Arguments	Action	Output
1	Query.user	id: "1"	Fetch user with id 1	{ id: "1", name: "Alice" }
2	User.name	user object	Return user name	"Alice"
3	User.posts	user object	Fetch posts for user id 1	[{ id: "101", title: "Hello World" }, { id: "102", title: "GraphQL Rocks" }]
4	Post.title (for post 101)	post object	Return post title	"Hello World"
5	Post.title (for post 102)	post object	Return post title	"GraphQL Rocks"
6	Return final response	assembled data	Send response to client	{ user: { name: "Alice", posts: [{ title: "Hello World" }, { title: "GraphQL Rocks" }] } }

💡 All requested fields resolved, final response assembled and sent to client.

Variable Tracker

Variable	Start	After Step 1	After Step 3	After Step 6
user	null	{ id: "1", name: "Alice" }	{ id: "1", name: "Alice" }	{ name: "Alice", posts: [...] }
posts	null	null	[{ id: "101", title: "Hello World" }, { id: "102", title: "GraphQL Rocks" }]	[{ title: "Hello World" }, { title: "GraphQL Rocks" }]
response	null	null	null	{ user: { name: "Alice", posts: [...] } }

Key Moments - 2 Insights

Why does the User.posts resolver run after User.name?

Because the query requests both fields, GraphQL calls each field's resolver separately in order, as shown in steps 2 and 3 of the execution_table.

How does the Post.title resolver know which post to process?

Each Post.title resolver receives a specific post object from the User.posts resolver, as shown in steps 4 and 5 where the input is the individual post object.

Visual Quiz - 3 Questions

Look at the execution_table, what is the output of the Query.user resolver at step 1?

A { id: "1", name: "Alice" }

B "Alice"

C [{ id: "101", title: "Hello World" }]

D null

💡 Hint

Check the Output column in row with Step 1 in execution_table.

At which step does the resolver fetch the list of posts for the user?

A Step 2

B Step 3

C Step 4

D Step 6

💡 Hint

Look at the Resolver Called and Action columns in execution_table.

If the user had no posts, how would the output at step 3 change?

A It would return null

B It would return an error

C It would return an empty list []

D It would return the user object

💡 Hint

Consider typical GraphQL behavior for empty lists in resolver outputs.

Concept Snapshot

Resolver chains in GraphQL:
- Each field in a query triggers its resolver.
- Resolvers run in order, passing data along.
- Nested fields call nested resolvers.
- Data flows up to form the final response.
- This chain ensures modular, stepwise data fetching.

Full Transcript

Resolver chains in GraphQL work by calling each resolver function for fields requested in a query. The process starts when the client sends a query. The GraphQL server parses it and calls the root resolver. This resolver fetches data and calls the next resolver in the chain for nested fields. Each resolver processes its data and returns results up the chain. Finally, the server assembles all data into the response sent back to the client. For example, a query asking for a user's name and posts triggers the user resolver, then the name resolver, then the posts resolver, and finally the title resolvers for each post. This step-by-step chain ensures each piece of data is fetched and combined correctly.

Practice

1. What is the main purpose of resolver chains in GraphQL?

easy

A. To speed up database indexing

B. To create new database tables automatically

C. To fetch data step-by-step using results from previous resolvers

D. To encrypt data before sending it to clients

Solution

1. Step 1: Understand resolver chains concept

   Resolver chains allow each resolver to use data from the previous resolver's result, enabling step-by-step data fetching.

2. Step 2: Compare options with concept

   Only To fetch data step-by-step using results from previous resolvers describes this stepwise data fetching using parent results, which matches the purpose of resolver chains.

3. Final Answer:

   To fetch data step-by-step using results from previous resolvers -> Option C

4. Quick Check:

   Resolver chains = step-by-step data fetching [OK]

Hint: Resolver chains pass data stepwise between resolvers [OK]

Common Mistakes:

• Confusing resolver chains with database indexing
• Thinking resolver chains create tables
• Assuming resolver chains encrypt data

2. Which of the following is the correct way to access the parent resolver's result in a GraphQL resolver function?

easy

A. function resolver(args, context) { ... }

B. function resolver(args, parent, context) { ... }

C. function resolver(context, args, parent) { ... }

D. function resolver(parent, args, context) { ... }

Solution

1. Step 1: Recall resolver function signature

   In GraphQL, the first argument to a resolver is the parent object, followed by args and context.

2. Step 2: Match signature with options

   Only function resolver(parent, args, context) { ... } correctly places parent as the first argument, allowing access to previous resolver's result.

3. Final Answer:

   function resolver(parent, args, context) { ... } -> Option D

4. Quick Check:

   Parent is first argument in resolver [OK]

Hint: Parent is always the first argument in resolver functions [OK]

Common Mistakes:

• Swapping order of arguments
• Omitting the parent argument
• Confusing context with parent

3. Given the following resolver chain, what will be the final output?

const resolvers = {
  Query: {
    user: () => ({ id: 1, name: 'Alice' })
  },
  User: {
    posts: (parent) => [
      { id: 101, title: 'Post 1', authorId: parent.id },
      { id: 102, title: 'Post 2', authorId: parent.id }
    ]
  }
};

// Query: { user { name posts { title } } }

medium

A. { user: { name: 'Alice', posts: [] } }

B. { user: { name: 'Alice', posts: [{ title: 'Post 1' }, { title: 'Post 2' }] } }

C. { user: { name: 'Alice', posts: [{ title: 'Post 1' }, { title: 'Post 2' }, { title: 'Post 3' }] } }

D. Error: Cannot read property 'id' of undefined

Solution

1. Step 1: Analyze user resolver output

   The user resolver returns an object with id 1 and name 'Alice'.

2. Step 2: Analyze posts resolver using parent

   The posts resolver receives parent with id 1, so it returns two posts with authorId 1 and titles 'Post 1' and 'Post 2'.

3. Final Answer:

   { user: { name: 'Alice', posts: [{ title: 'Post 1' }, { title: 'Post 2' }] } } -> Option B

4. Quick Check:

   Posts use parent.id = 1, two posts returned [OK]

Hint: Parent contains previous resolver's data for next resolver [OK]

Common Mistakes:

• Assuming posts resolver returns three posts
• Expecting empty posts array
• Confusing parent argument as undefined

4. Identify the error in this resolver chain code snippet:

const resolvers = {
  Query: {
    book: () => ({ id: 5, title: 'GraphQL Guide' })
  },
  Book: {
    author: (args) => {
      return { id: 2, name: 'John Doe' };
    }
  }
};

medium

A. The author resolver is missing the parent argument

B. The book resolver should return a list, not an object

C. The author resolver should not return an object

D. The Query resolver should have three arguments

Solution

1. Step 1: Check author resolver signature

   The author resolver should receive the parent object as the first argument to access book data.

2. Step 2: Identify missing parent argument

   Here, author resolver only has args, so it cannot access parent data, breaking the resolver chain.

3. Final Answer:

   The author resolver is missing the parent argument -> Option A

4. Quick Check:

   Resolvers need parent as first argument [OK]

Hint: Always include parent as first argument in chained resolvers [OK]

Common Mistakes:

• Ignoring parent argument in nested resolvers
• Thinking book resolver must return a list
• Assuming author resolver cannot return objects

5. You want to fetch a list of orders with their customer names using resolver chains. The orders resolver returns an array of orders with customerId. How should you implement the customer resolver to correctly use resolver chains?

hard

A. Use the parent argument to get customerId and fetch customer data from database

B. Ignore the parent argument and fetch all customers in the customer resolver

C. Pass customerId as an argument to the orders resolver

D. Return a static customer object without using parent data

Solution

1. Step 1: Understand data flow in resolver chains

   The orders resolver returns orders with customerId; the customer resolver uses parent to access customerId.

2. Step 2: Use parent argument in customer resolver

   The customer resolver should use parent.customerId to fetch the correct customer data from the database.

3. Final Answer:

   Use the parent argument to get customerId and fetch customer data from database -> Option A

4. Quick Check:

   Parent passes customerId to customer resolver [OK]

Hint: Use parent.customerId in customer resolver to fetch data [OK]

Common Mistakes:

• Fetching all customers instead of one
• Ignoring parent and missing customerId
• Returning static data ignoring dynamic parent info