Why resolvers connect schema to data in GraphQL - Quick Recap

Recall & Review

beginner

What is the main role of a resolver in GraphQL?

A resolver connects the GraphQL schema to the actual data by fetching or computing the data for each field requested.

beginner

Why can't the GraphQL schema fetch data by itself?

The schema only defines the shape and types of data but does not know how or where to get the data; resolvers handle this connection.

intermediate

How do resolvers help in separating concerns in a GraphQL API?

Resolvers separate the data fetching logic from the schema definition, making the API easier to maintain and update.

intermediate

What happens if a resolver is missing for a field in GraphQL?

If no resolver is provided, GraphQL uses a default resolver that tries to return a property with the same name from the parent object.

advanced

Can resolvers fetch data from multiple sources? Why is this useful?

Yes, resolvers can fetch data from databases, APIs, or other services, allowing GraphQL to unify data from many places into one response.

What does a resolver do in GraphQL?

A Defines the data types in the schema

B Fetches or computes data for a schema field

C Validates user input

D Creates database tables

Resolvers are functions that fetch or compute the data for each field defined in the GraphQL schema.

If a field in the schema has no resolver, what happens?

A The field is ignored

B GraphQL throws an error

C GraphQL uses a default resolver to return a matching property

D The server crashes

GraphQL uses a default resolver that returns the property with the same name from the parent object if no custom resolver is provided.

Why is it useful that resolvers can fetch data from multiple sources?

A It speeds up the schema definition

B It makes the schema smaller

C It prevents errors in queries

D It allows combining data from different places in one response

Resolvers can gather data from databases, APIs, or other services, enabling GraphQL to unify diverse data sources.

What part of GraphQL defines the shape and types of data?

A Schema

B Mutations

C Queries

D Resolvers

The schema defines the structure and data types but does not fetch data itself.

How do resolvers improve maintainability of a GraphQL API?

A By separating data fetching logic from schema

B By mixing data fetching with schema definition

C By removing the need for a schema

D By caching all data automatically

Resolvers keep data fetching logic separate from the schema, making the API easier to update and maintain.

Explain why resolvers are necessary to connect a GraphQL schema to actual data.

Think about what the schema can and cannot do by itself.

Describe how resolvers help manage data from multiple sources in a GraphQL API.

Consider how data might come from databases, external APIs, or other services.

Practice

1. What is the main role of a resolver in GraphQL?

easy

A. To fetch or compute the data for a specific field in the schema

B. To define the structure of the GraphQL schema

C. To handle user authentication and authorization

D. To format the query string before execution

Solution

1. Step 1: Understand the purpose of resolvers

   Resolvers are functions that run when a field in the schema is requested to provide the actual data.

2. Step 2: Differentiate from schema definition

   The schema defines the shape of data, but resolvers connect those fields to real data sources or computations.

3. Final Answer:

   To fetch or compute the data for a specific field in the schema -> Option A

4. Quick Check:

   Resolvers fetch data = A [OK]

Hint: Resolvers provide data for fields, not schema or auth [OK]

Common Mistakes:

• Confusing resolvers with schema definitions
• Thinking resolvers handle authentication
• Believing resolvers format queries

2. Which of the following is the correct syntax for a simple resolver function in GraphQL?

easy

A. const resolver = (parent; args; context) => data;

B. const resolver = { parent, args, context } => data;

C. const resolver = (parent, args, context) => data;

D. const resolver = (parent args context) => data;

Solution

1. Step 1: Recall JavaScript arrow function syntax

   Arrow functions use parentheses for parameters separated by commas, e.g., (a, b, c) => result.

2. Step 2: Check each option's parameter syntax

   const resolver = (parent, args, context) => data; uses commas correctly; A uses semicolons instead of commas; B uses braces instead of parentheses; D misses commas.

3. Final Answer:

   const resolver = (parent, args, context) => data; -> Option C

4. Quick Check:

   Arrow function params need commas = C [OK]

Hint: Arrow function params need commas inside parentheses [OK]

Common Mistakes:

• Using braces {} instead of parentheses () for parameters
• Separating parameters with semicolons
• Omitting commas between parameters

3. Given this resolver snippet, what will be the output when querying userName?

const resolvers = {
  Query: {
    userName: () => "Alice"
  }
};

medium

A. "Alice"

B. "userName"

C. null

D. Error: resolver not found

Solution

1. Step 1: Identify the resolver function for userName

   The resolver for userName returns the string "Alice" directly.

2. Step 2: Understand the query result

   When the userName field is queried, the resolver returns "Alice", so the output is "Alice".

3. Final Answer:

   "Alice" -> Option A

4. Quick Check:

   Resolver returns "Alice" = B [OK]

Hint: Resolver return value is the query output [OK]

Common Mistakes:

• Confusing field name with returned value
• Expecting null if no arguments
• Assuming error without resolver

4. Identify the error in this resolver code snippet:

const resolvers = {
  Query: {
    userAge: (parent, args) => {
      return args.age
    }
  }
};

// Query: { userAge }
// Variables: {}

medium

A. Missing context parameter in resolver

B. Resolver expects argument 'age' but none provided in query

C. Resolver should return parent instead of args.age

D. Syntax error: missing semicolon after return

Solution

1. Step 1: Check resolver parameters and usage

   The resolver expects an argument named 'age' from args to return.

2. Step 2: Analyze the query and variables

   The query requests userAge but provides no variables, so args.age is undefined.

3. Final Answer:

   Resolver expects argument 'age' but none provided in query -> Option B

4. Quick Check:

   Missing argument in query = D [OK]

Hint: Check if query provides needed args for resolver [OK]

Common Mistakes:

• Assuming context is always required
• Ignoring missing query variables
• Thinking missing semicolon causes error here

5. You want to fetch a user's full profile by combining data from two sources: a database and an external API. How should you design the resolver for the userProfile field?

hard

A. Fetch data only from the database and ignore the API

B. Define the schema to include both data sources without a resolver

C. Use two separate resolvers for the same field to fetch data independently

D. Write a resolver that calls the database and API, then merges results before returning

Solution

1. Step 1: Understand resolver role in combining data

   Resolvers can run code to fetch and combine data from multiple sources before returning.

2. Step 2: Evaluate options for fetching and merging data

   Write a resolver that calls the database and API, then merges results before returning correctly describes writing a resolver that calls both sources and merges results. Other options either ignore data sources or misuse resolvers.

3. Final Answer:

   Write a resolver that calls the database and API, then merges results before returning -> Option D

4. Quick Check:

   Resolvers combine data sources = A [OK]

Hint: Combine data in one resolver function for the field [OK]

Common Mistakes:

• Expecting schema alone to fetch data
• Trying multiple resolvers for one field
• Ignoring one data source