Default resolvers in GraphQL - Step-by-Step Execution

Concept Flow - Default resolvers

GraphQL Query Received

↓

Check Field Resolver

↓

Use Custom

↓

Fetch Data

↓

Return Result

When a GraphQL query runs, it looks for a custom resolver for each field. If none is found, it uses the default resolver which returns the field value from the parent object.

Execution Sample

GraphQL

query {
  user {
    id
    name
  }
}

This query asks for a user's id and name. If no custom resolver exists for 'id' or 'name', default resolvers return those fields from the user object.

Execution Table

Step	Field	Custom Resolver?	Action	Result
1	user	No	Use default resolver to get 'user' object	{ id: 1, name: "Alice" }
2	id	No	Use default resolver to get 'id' from user object	1
3	name	No	Use default resolver to get 'name' from user object	"Alice"
4	Query complete	-	-	Return { user: { id: 1, name: "Alice" } }

💡 All fields resolved; query result assembled and returned.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
user	undefined	{ id: 1, name: "Alice" }	{ id: 1, name: "Alice" }	{ id: 1, name: "Alice" }	{ id: 1, name: "Alice" }
id	undefined	undefined	1	1	1
name	undefined	undefined	undefined	"Alice"	"Alice"

Key Moments - 2 Insights

Why does the default resolver return the field value from the parent object?

Because when no custom resolver is defined (see execution_table steps 2 and 3), the default resolver simply looks up the field name in the parent object and returns its value.

What happens if a custom resolver exists for a field?

If a custom resolver exists (not shown in this example), GraphQL calls that resolver function instead of the default one to get the field's value.

Visual Quiz - 3 Questions

Look at the execution table, what is the result of resolving the 'name' field at step 3?

A 1

B undefined

C "Alice"

D Error

💡 Hint

Check the 'Result' column for step 3 in the execution_table.

At which step does the 'user' object get fetched using the default resolver?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Look at the 'Field' and 'Action' columns in the execution_table.

If a custom resolver was added for 'name', how would the execution_table change?

A Step 3 would show 'Yes' under 'Custom Resolver?' and call the custom function.

B Step 2 would change to use the custom resolver.

C Step 1 would return an error.

D No changes; default resolver always runs.

💡 Hint

Recall the concept_flow where custom resolvers override default ones.

Concept Snapshot

Default resolvers in GraphQL automatically return the field's value from the parent object if no custom resolver is defined.
When a query runs, each field checks for a custom resolver.
If none exists, the default resolver returns parent[fieldName].
This simplifies schema design by avoiding boilerplate for simple fields.
Custom resolvers are only needed for computed or complex fields.

Full Transcript

When a GraphQL query is executed, each field is resolved by checking if a custom resolver function exists. If it does, that function is called to get the field's value. If not, the default resolver is used, which simply returns the value of the field from the parent object. For example, in a query requesting a user's id and name, if no custom resolvers exist for these fields, the default resolver returns the 'id' and 'name' properties from the user object. This process continues for all fields until the full query result is assembled and returned. This behavior allows simple fields to be resolved automatically without extra code, while still supporting custom logic when needed.

Practice

1. What is the main purpose of default resolvers in GraphQL?

easy

A. To write custom logic for every field in the schema

B. To automatically return data by matching schema fields to data keys

C. To validate user input before querying the database

D. To handle errors during query execution

Solution

1. Step 1: Understand default resolver behavior

   Default resolvers automatically map schema fields to matching data keys without extra code.

2. Step 2: Compare with other options

   Options B, C, and D describe custom logic, validation, and error handling, which are not default resolver roles.

3. Final Answer:

   To automatically return data by matching schema fields to data keys -> Option B

4. Quick Check:

   Default resolver = automatic field-to-key mapping [OK]

Hint: Default resolvers match schema fields to data keys automatically [OK]

Common Mistakes:

• Thinking default resolvers handle validation
• Confusing default resolvers with custom resolvers
• Assuming default resolvers manage errors

2. Which of the following is the correct way to define a GraphQL schema field that uses a default resolver?

easy

A. type Query { user: User() }

B. type Query { user: User @customResolver }

C. type Query { user: User }

D. type Query { user: User -> resolver }

Solution

1. Step 1: Identify correct schema syntax

   GraphQL schema fields are defined as fieldName: Type without extra syntax for default resolvers.

2. Step 2: Analyze options

   type Query { user: User } uses correct syntax. Options B, C, and D include invalid or non-standard syntax.

3. Final Answer:

   type Query { user: User } -> Option C

4. Quick Check:

   Default resolver needs simple field: Type syntax [OK]

Hint: Default resolvers need simple field: Type syntax in schema [OK]

Common Mistakes:

• Adding parentheses after type name
• Using custom directives without definition
• Using arrow or other symbols in schema

3. Given the schema type Query { book: Book } and data { book: { title: "1984", author: "Orwell" } }, what will the default resolver return for the field book?

medium

A. { title: "1984", author: "Orwell" }

B. "1984"

C. null

D. Error: Resolver not found

Solution

1. Step 1: Understand default resolver behavior

   The default resolver returns the data object matching the field name if it exists.

2. Step 2: Match field to data

   The field book matches the data key book which contains the object with title and author.

3. Final Answer:

   { title: "1984", author: "Orwell" } -> Option A

4. Quick Check:

   Field book returns matching data object [OK]

Hint: Default resolver returns matching data object for field name [OK]

Common Mistakes:

• Returning only one property instead of whole object
• Expecting null if no custom resolver is defined
• Assuming error if resolver is not explicitly written

4. You wrote a GraphQL schema with type Query { user: User } but your query returns null for user. What is a likely cause related to default resolvers?

medium

A. The data source does not have a matching key named 'user'

B. You forgot to write a custom resolver for 'user'

C. The schema syntax is invalid

D. GraphQL does not support default resolvers

Solution

1. Step 1: Recall default resolver behavior

   Default resolvers return data matching the field name from the data source.

2. Step 2: Identify cause of null result

   If the data source lacks a key named 'user', the default resolver returns null.

3. Final Answer:

   The data source does not have a matching key named 'user' -> Option A

4. Quick Check:

   Missing data key causes null from default resolver [OK]

Hint: Check data keys match schema fields for default resolver to work [OK]

Common Mistakes:

• Assuming custom resolver is always required
• Blaming schema syntax without checking data
• Thinking default resolvers are unsupported

5. You have a schema type Query { product: Product } and data { product: { id: 1, name: "Pen", price: 2.5 } }. You want to return the price with a 10% discount but keep default resolvers for other fields. How should you implement this?

hard

A. Use default resolvers only; custom resolvers cannot be mixed

B. Write a custom resolver for the entire 'product' field in Query

C. Modify the data source to store discounted price

D. Write a custom resolver only for the 'price' field inside Product type

Solution

1. Step 1: Understand resolver layering

   Default resolvers work per field; you can override specific fields with custom resolvers.

2. Step 2: Apply custom resolver to 'price' only

   Write a custom resolver for 'price' to apply discount, leaving other fields to default resolvers.

3. Step 3: Avoid overriding entire 'product' resolver

   Overriding entire 'product' would require manually returning all fields, losing default resolver benefits.

4. Final Answer:

   Write a custom resolver only for the 'price' field inside Product type -> Option D

5. Quick Check:

   Custom resolver per field + default resolvers for others [OK]

Hint: Override only needed fields with custom resolvers, keep defaults for rest [OK]

Common Mistakes:

• Overriding entire parent field unnecessarily
• Trying to mix default and custom resolvers at root level only
• Modifying data source instead of resolver logic