Info argument in GraphQL - Time & Space Complexity

Time Complexity: Info argument

O(n)

Understanding Time Complexity

When using the info argument in GraphQL resolvers, it's important to understand how the time to process requests grows as the data size increases.

We want to know how the operations inside the resolver scale when the info argument is used.

Scenario Under Consideration

Analyze the time complexity of this GraphQL resolver using the info argument.

const resolver = (parent, args, context, info) => {
  const fields = info.fieldNodes[0].selectionSet.selections;
  return fetchData(fields);
};

This resolver extracts requested fields from the info argument and fetches data accordingly.

Identify Repeating Operations

Look at what repeats when processing the info argument.

• Primary operation: Looping over the selections array inside info.fieldNodes[0].selectionSet.selections.
• How many times: Once per requested field in the query.

How Execution Grows With Input

As the number of requested fields grows, the loop runs more times.

Input Size (n)	Approx. Operations
10 fields	10 loops
100 fields	100 loops
1000 fields	1000 loops

Pattern observation: The operations grow directly with the number of requested fields.

Final Time Complexity

Time Complexity: O(n)

This means the time to process the info argument grows linearly with the number of fields requested.

Common Mistake

[X] Wrong: "Processing the info argument takes constant time no matter how many fields are requested."

[OK] Correct: Because the resolver loops through each requested field, more fields mean more work, so time grows with the number of fields.

Interview Connect

Understanding how the info argument affects performance shows you can reason about query costs and optimize data fetching in real projects.

Self-Check

"What if the resolver also recursively processes nested selections inside info? How would that affect the time complexity?"

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