[Solved] Find the bug in this resolver:const resolver = (parent, args, context) => { const userId = context.userId; return context.db.getUser(userId); }Assuming context.userId is undefined. | GraphQL

GraphQL - Resolvers

Find the bug in this resolver:

const resolver = (parent, args, context) => {
  const userId = context.userId;
  return context.db.getUser(userId);
}

Assuming context.userId is undefined.

AMissing <code>args</code> parameter

BUsing <code>context.userId</code> instead of <code>context.user.id</code>

CResolver should be async

DIncorrect return statement syntax

Step-by-Step Solution

Solution:

Step 1: Identify the property used from context
The code uses context.userId, but context likely stores user info under context.user.id.
Step 2: Understand undefined userId causes wrong DB call
Since context.userId is undefined, the DB call will fail or return wrong data.
Final Answer:
Using context.userId instead of context.user.id -> Option B
Quick Check:
Correct context property usage fixes bug [OK]

Quick Trick: Use correct context property names [OK]

Common Mistakes:

Master "Resolvers" in GraphQL

9 interactive learning modes - each teaches the same concept differently

More GraphQL Quizzes

Find the bug in this resolver: