Info argument in GraphQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Info argument in GraphQL resolvers?

The Info argument is an object passed to GraphQL resolver functions that contains details about the execution state, including the query's AST, field name, path, and schema information.

intermediate

Which of these is NOT part of the Info argument in GraphQL?

The Info argument includes the field name, the query's abstract syntax tree (AST), the schema, and the path to the field. It does not include the database connection or context data.

intermediate

How can the Info argument help optimize data fetching in GraphQL?

By inspecting the Info argument's field nodes, resolvers can determine exactly which fields the client requested, allowing them to fetch only necessary data and avoid over-fetching.

beginner

True or False: The Info argument contains the context object passed to GraphQL resolvers.

False. The context object is a separate argument passed to resolvers. The Info argument contains execution details like the query AST and field path.

beginner

In a resolver function signature resolve(parent, args, context, info), what does info represent?

The info parameter provides metadata about the current query execution, such as the field name, query AST, schema, and path, helping the resolver understand the query structure.

What does the Info argument in a GraphQL resolver contain?

A User authentication data

B HTTP request headers

C Database connection details

D Details about the query execution like field name and AST

The Info argument contains details about the query execution such as the field name, query AST, schema, and path.

Which argument in a GraphQL resolver provides the query's abstract syntax tree (AST)?

A parent

B args

C info

D context

The info argument contains the query's AST, which describes the structure of the query.

Can the Info argument be used to determine which fields the client requested in a query?

A Yes, by inspecting the field nodes

B No, it only contains context data

C No, it only contains parent data

D Yes, but only for mutations

The Info argument includes field nodes that show exactly which fields the client requested.

Is the context object part of the Info argument in GraphQL resolvers?

A Yes, always

B No, context is a separate argument

C Only in subscriptions

D Only in mutations

Context is passed as a separate argument to resolvers, not inside the Info argument.

Which of these is NOT a typical use of the Info argument?

A Fetching user authentication info

B Getting the field name being resolved

C Accessing the query's AST

D Determining the path to the current field

User authentication info is usually stored in the context, not in the Info argument.

Explain what the Info argument is in GraphQL resolvers and why it is useful.

Think about what extra information a resolver might need about the query.

Describe the difference between the Info argument and the Context argument in GraphQL resolvers.

One is about the query structure, the other about shared environment.

Practice

1. What is the purpose of the info argument in a GraphQL resolver?

easy

A. It stores the database connection details.

B. It contains the user's authentication token.

C. It tells the resolver which fields the client requested.

D. It defines the schema of the GraphQL server.

Solution

1. Step 1: Understand the role of resolver arguments

   Resolvers receive arguments like parent, args, context, and info. Each has a specific role.

2. Step 2: Identify what info provides

   The info argument contains details about the query, including which fields the client requested.

3. Final Answer:

   It tells the resolver which fields the client requested. -> Option C

4. Quick Check:

   Info argument = requested fields [OK]

Hint: Info shows requested fields to optimize data fetching [OK]

Common Mistakes:

• Confusing info with context or args
• Thinking info holds authentication data
• Assuming info defines schema

2. Which of the following is the correct way to include the info argument in a GraphQL resolver function?

easy

A. resolver(parent, args, context, info) { ... }

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

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

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

Solution

1. Step 1: Recall the standard resolver signature

   The standard order is (parent, args, context, info) in GraphQL resolvers.

2. Step 2: Match the correct order

   resolver(parent, args, context, info) { ... } matches this order exactly, making it the correct syntax.

3. Final Answer:

   resolver(parent, args, context, info) { ... } -> Option A

4. Quick Check:

   Resolver args order = parent, args, context, info [OK]

Hint: Remember resolver args order: parent, args, context, info [OK]

Common Mistakes:

• Mixing up the order of arguments
• Placing info before context
• Omitting info argument

3. Given this resolver snippet, what will info.fieldNodes[0].selectionSet.selections.map(f => f.name.value) return if the client queries { user { id name } }?

medium

A. ["id", "name"]

B. ["user"]

C. ["id"]

D. An empty array []

Solution

1. Step 1: Understand the query structure

   The client requests the fields id and name inside user.

2. Step 2: Analyze the info.fieldNodes access

   info.fieldNodes[0].selectionSet.selections lists the fields requested inside user, which are id and name.

3. Final Answer:

   ["id", "name"] -> Option A

4. Quick Check:

   info.fieldNodes selections = requested fields [OK]

Hint: info.fieldNodes lists requested fields inside current resolver [OK]

Common Mistakes:

• Returning parent field name instead of subfields
• Confusing selectionSet with fieldNodes
• Expecting only one field instead of all requested

4. You wrote this resolver: function resolver(parent, args, context) { return info.fieldNodes; }. Why does this cause an error?

medium

A. You cannot access fieldNodes inside resolvers.

B. The resolver is missing the info argument in its parameters.

C. The info argument must be the first parameter.

D. Resolvers cannot return objects like fieldNodes.

Solution

1. Step 1: Check resolver parameters

   The resolver only has three parameters: parent, args, context. It lacks the fourth parameter info.

2. Step 2: Understand usage of info

   Since info is not declared, trying to use it causes a reference error.

3. Final Answer:

   The resolver is missing the info argument in its parameters. -> Option B

4. Quick Check:

   Missing info param = error [OK]

Hint: Always include info as fourth parameter to use it [OK]

Common Mistakes:

• Forgetting to add info parameter
• Assuming info is global or in context
• Misordering resolver parameters

5. You want your resolver to return only the fields requested by the client to save resources. Which approach using the info argument is best?

hard

A. Fetch all fields but filter results after sending to client.

B. Ignore info and always fetch all fields from the database.

C. Use args to guess which fields the client wants.

D. Use info.fieldNodes to find requested fields and fetch only those from the database.

Solution

1. Step 1: Understand the goal

   The goal is to fetch only requested fields to save resources.

2. Step 2: Use info to get requested fields

   info.fieldNodes provides the exact fields the client asked for, so you can fetch only those.

3. Step 3: Compare options

   Use info.fieldNodes to find requested fields and fetch only those from the database. uses info correctly. Options B, C, and D either waste resources or guess incorrectly.

4. Final Answer:

   Use info.fieldNodes to find requested fields and fetch only those from the database. -> Option D

5. Quick Check:

   Use info to fetch requested fields only [OK]

Hint: Fetch only requested fields using info to save resources [OK]

Common Mistakes:

• Fetching all data regardless of request
• Using args instead of info for fields
• Filtering after fetching all data