Resolver organization in GraphQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a resolver in GraphQL?

A resolver is a function that tells GraphQL how to fetch or compute the data for a specific field in a query.

beginner

Why organize resolvers in separate files or folders?

Organizing resolvers separately helps keep code clean, easier to maintain, and allows teams to work on different parts without conflicts.

intermediate

What is the common pattern to group resolvers by type?

Resolvers are often grouped by GraphQL types like Query, Mutation, and custom types, each in their own file or object.

intermediate

How does modular resolver organization improve teamwork?

It allows multiple developers to work on different resolver files without overwriting each other's code, making collaboration smoother.

intermediate

What is a resolver map in GraphQL?

A resolver map is an object that connects GraphQL types and fields to their resolver functions, often combined from multiple files.

What does a resolver function do in GraphQL?

A Fetches or computes data for a field

B Defines the GraphQL schema

C Validates user input

D Styles the UI components

Resolvers fetch or compute the data for each field requested in a GraphQL query.

Which is a good practice for organizing resolvers?

A Group resolvers by GraphQL types like Query and Mutation

B Put all resolvers in one huge file

C Write resolvers inside HTML files

D Avoid using resolver functions

Grouping resolvers by types like Query and Mutation keeps code organized and easier to maintain.

What is a resolver map?

A A list of database tables

B A map of UI components

C A GraphQL query

D An object linking types and fields to resolver functions

A resolver map connects GraphQL types and fields to their resolver functions.

How does modular resolver organization help teams?

A It slows down development

B It makes code harder to read

C It allows multiple developers to work without conflicts

D It removes the need for testing

Modular organization lets developers work on different parts without overwriting each other's code.

Which folder structure is best for resolver organization?

A /resolvers/allResolvers.js (one big file)

B /resolvers/Query.js, /resolvers/Mutation.js

C /resolvers/styles.css

D /resolvers/index.html

Separating Query and Mutation resolvers into their own files is a common and clear practice.

Explain how you would organize resolvers in a GraphQL project for clarity and teamwork.

Think about dividing work like organizing chapters in a book.

Describe what a resolver map is and why it is useful.

Imagine a map that shows where each resolver lives.

Practice

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

easy

A. To connect schema fields to the actual data sources

B. To define the GraphQL schema types and fields

C. To handle client-side state management

D. To style the GraphQL playground interface

Solution

1. Step 1: Understand the role of resolvers

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

2. Step 2: Identify what resolvers connect

   Resolvers connect the schema fields to the actual data sources like databases or APIs.

3. Final Answer:

   To connect schema fields to the actual data sources -> Option A

4. Quick Check:

   Resolvers = Connect schema to data [OK]

Hint: Resolvers link schema fields directly to data sources [OK]

Common Mistakes:

• Confusing resolvers with schema definitions
• Thinking resolvers handle UI or styling
• Assuming resolvers manage client state

2. Which of the following is the correct way to organize resolvers in a GraphQL server?

easy

A. Group resolvers by Query, Mutation, and type names

B. Put all resolvers in a single flat list without grouping

C. Write resolvers only inside the schema definition file

D. Use one resolver function for the entire schema

Solution

1. Step 1: Recognize common resolver organization

   Resolvers are typically grouped by operation types: Query, Mutation, and by object types for clarity.

2. Step 2: Evaluate the options

   Grouping by Query, Mutation, and types helps maintain and scale the server easily.

3. Final Answer:

   Group resolvers by Query, Mutation, and type names -> Option A

4. Quick Check:

   Organize resolvers by operation type [OK]

Hint: Group resolvers by Query, Mutation, and types for clarity [OK]

Common Mistakes:

• Putting all resolvers in one list without grouping
• Mixing resolver code inside schema files
• Using a single resolver for all fields

3. Given this resolver structure:

const resolvers = {
  Query: {
    user: () => ({ id: 1, name: "Alice" })
  },
  User: {
    fullName: (parent) => parent.name + " Smith"
  }
};

What will be the result of querying { user { fullName } }?

medium

A. Error: Resolver for fullName missing

B. { "user": { "fullName": "Smith" } }

C. { "user": { "fullName": null } }

D. { "user": { "fullName": "Alice Smith" } }

Solution

1. Step 1: Understand the Query resolver

   The Query resolver returns a user object with id 1 and name "Alice".

2. Step 2: Understand the User type resolver

   The User resolver for fullName appends " Smith" to the parent's name, resulting in "Alice Smith".

3. Final Answer:

   { "user": { "fullName": "Alice Smith" } } -> Option D

4. Quick Check:

   fullName = parent.name + " Smith" [OK]

Hint: User resolver uses parent data to build fullName [OK]

Common Mistakes:

• Forgetting to use parent argument in field resolver
• Expecting fullName to be directly in Query resolver
• Assuming missing resolver causes error

4. Consider this resolver code snippet:

const resolvers = {
  Query: {
    posts: () => fetchPosts()
  },
  Post: {
    author: () => fetchAuthor()
  }
};

What is the main problem with this resolver organization?

medium

A. The schema is missing a Subscription resolver

B. The Post.author resolver ignores the parent post and fetches unrelated author data

C. Resolvers must be async functions, but these are not

D. The Query.posts resolver should be inside Mutation

Solution

1. Step 1: Analyze Post.author resolver

   The author resolver does not use the parent post argument, so it cannot fetch the correct author for each post.

2. Step 2: Understand resolver context

   Field resolvers should use the parent argument to access related data; ignoring it causes wrong or unrelated data.

3. Final Answer:

   The Post.author resolver ignores the parent post and fetches unrelated author data -> Option B

4. Quick Check:

   Use parent argument in nested resolvers [OK]

Hint: Nested resolvers must use parent to access related data [OK]

Common Mistakes:

• Ignoring parent argument in nested resolvers
• Misplacing Query resolvers inside Mutation
• Assuming all resolvers must be async

5. You want to organize resolvers for a GraphQL server with Queries, Mutations, and a custom type Book. Which structure below best supports maintainability and scalability?

hard

A. const resolvers = { Query: {...}, Mutation: {...} }; // no Book resolvers

B. const resolvers = { allResolvers: {...} };

C. const resolvers = { Query: {...}, Mutation: {...}, Book: {...} };

D. const resolvers = { Book: {...} }; // no Query or Mutation

Solution

1. Step 1: Identify best practice for resolver organization

   Grouping resolvers by operation type (Query, Mutation) and by custom types (Book) keeps code clear and modular.

2. Step 2: Compare options

   const resolvers = { Query: {...}, Mutation: {...}, Book: {...} }; clearly separates concerns and allows easy updates and scaling.

3. Final Answer:

   const resolvers = { Query: {...}, Mutation: {...}, Book: {...} }; -> Option C

4. Quick Check:

   Separate resolvers by operation and type [OK]

Hint: Group resolvers by Query, Mutation, and types for best structure [OK]

Common Mistakes:

• Putting all resolvers in one object without grouping
• Omitting resolvers for custom types
• Ignoring Mutation resolvers