Input types in GraphQL - Time & Space Complexity

Time Complexity: Input types

O(n)

Understanding Time Complexity

When using input types in GraphQL, it's important to understand how the size of the input affects the work the server does.

We want to know how the server's effort grows as the input data gets bigger.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

input UserInput {
  name: String!
  emails: [String!]!
}

mutation addUser($input: UserInput!) {
  addUser(input: $input) {
    id
    name
  }
}

This mutation accepts a user input with a name and a list of emails, then adds the user.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Processing each email in the emails list.
• How many times: Once for each email in the input list.

How Execution Grows With Input

As the number of emails grows, the server does more work to handle each one.

Input Size (n)	Approx. Operations
10	Processes 10 emails
100	Processes 100 emails
1000	Processes 1000 emails

Pattern observation: The work grows directly with the number of emails.

Final Time Complexity

Time Complexity: O(n)

This means the time to process the input grows in a straight line with the number of emails.

Common Mistake

[X] Wrong: "The input size does not affect the time because it's just one mutation call."

[OK] Correct: Even though it's one call, the server must handle each email inside the input, so more emails mean more work.

Interview Connect

Understanding how input size affects server work helps you explain performance clearly and shows you think about real user data.

Self-Check

"What if the emails list was nested inside another list? How would that change the time complexity?"

Practice

1. What is the main purpose of input types in GraphQL?

easy

A. To define the shape of data sent into queries or mutations

B. To specify the output format of queries

C. To create database tables automatically

D. To style the API responses

Solution

1. Step 1: Understand the role of input types

   Input types define how data should be structured when sent to the server in queries or mutations.

2. Step 2: Differentiate input from output types

   Output types define what data is returned, while input types organize incoming data.

3. Final Answer:

   To define the shape of data sent into queries or mutations -> Option A

4. Quick Check:

   Input types = organize incoming data [OK]

Hint: Input types shape incoming data, not output [OK]

Common Mistakes:

• Confusing input types with output types
• Thinking input types create database tables
• Assuming input types affect response styling

2. Which of the following is the correct syntax to define an input type in GraphQL?

easy

A. input UserInput = { name: String!, age: Int }

B. type UserInput { name: String! age: Int }

C. input UserInput(name: String!, age: Int)

D. input UserInput { name: String! age: Int }

Solution

1. Step 1: Recall input type declaration syntax

   Input types use the keyword input followed by the name and curly braces for fields.

2. Step 2: Check each option's syntax

   input UserInput { name: String! age: Int } correctly uses input UserInput { ... }. type UserInput { name: String! age: Int } uses type which is for output types. Options C and D have invalid syntax.

3. Final Answer:

   input UserInput { name: String! age: Int } -> Option D

4. Quick Check:

   Input types start with 'input' keyword [OK]

Hint: Input types start with 'input' keyword and braces [OK]

Common Mistakes:

• Using 'type' instead of 'input'
• Using parentheses instead of braces
• Assigning input type with '=' sign

3. Given this input type:

input ProductInput { id: ID! name: String! price: Float }

Which mutation call is valid?

medium

A. mutation { addProduct(input: { name: "Pen", price: "1.5" }) { id name } }

B. mutation { addProduct(input: { id: 123, name: "Pen" }) { id name } }

C. mutation { addProduct(input: { id: "123", name: "Pen", price: 1.5 }) { id name } }

D. mutation { addProduct(input: { id: "123", price: 1.5 }) { id name } }

Solution

1. Step 1: Check required fields and types

   Fields id and name are required (non-null). price is optional. Types must match: id is ID (string), name is String, price is Float.

2. Step 2: Validate each option

   mutation { addProduct(input: { id: "123", name: "Pen", price: 1.5 }) { id name } } provides all required fields with correct types. mutation { addProduct(input: { id: 123, name: "Pen" }) { id name } } uses number 123 for ID (should be string). mutation { addProduct(input: { name: "Pen", price: "1.5" }) { id name } } misses required id and uses string for price (should be Float). mutation { addProduct(input: { id: "123", price: 1.5 }) { id name } } misses required name.

3. Final Answer:

   mutation { addProduct(input: { id: "123", name: "Pen", price: 1.5 }) { id name } } -> Option C

4. Quick Check:

   Required fields present with correct types [OK]

Hint: Required fields must be present with correct types [OK]

Common Mistakes:

• Omitting required fields
• Using wrong data types (e.g., number instead of string for ID)
• Passing strings for Float fields

4. Identify the error in this input type definition:

input UserInput { id: ID! name: String age: Int! }

medium

A. Syntax is correct; no error

B. Input types cannot have non-null fields

C. Missing commas between fields

D. Field names must be lowercase

Solution

1. Step 1: Review GraphQL input type syntax rules

   Input types list fields with their types separated by spaces or new lines; commas are not required.

2. Step 2: Check each option against syntax

   Input types cannot have non-null fields is false; non-null fields are allowed. Field names must be lowercase is false; field names can be camelCase or lowercase. Missing commas between fields is false; commas are optional. Syntax is correct; no error is true; the syntax is valid.

3. Final Answer:

   Syntax is correct; no error -> Option A

4. Quick Check:

   Input fields separated by spaces, commas optional [OK]

Hint: Commas are optional between fields in input types [OK]

Common Mistakes:

• Thinking commas are mandatory
• Believing non-null fields are disallowed
• Assuming field names must be lowercase only

5. You want to create an input type for updating a user's profile where all fields are optional except id. Which input type definition is correct?

hard

A. input UpdateUserInput { id: ID! name: String! email: String age: Int }

B. input UpdateUserInput { id: ID! name: String email: String age: Int }

C. input UpdateUserInput { id: ID! name: String! email: String! age: Int! }

D. input UpdateUserInput { id: ID name: String! email: String! age: Int! }

Solution

1. Step 1: Understand requirement for optional fields

   Only id must be required (non-null). Other fields should be optional, so no exclamation marks.

2. Step 2: Evaluate each option

   input UpdateUserInput { id: ID! name: String email: String age: Int } has id: ID! required and others optional. input UpdateUserInput { id: ID name: String! email: String! age: Int! } makes id optional and others required, wrong. input UpdateUserInput { id: ID! name: String! email: String! age: Int! } makes all fields required, wrong. input UpdateUserInput { id: ID! name: String! email: String age: Int } makes name required, which is not desired.

3. Final Answer:

   input UpdateUserInput { id: ID! name: String email: String age: Int } -> Option B

4. Quick Check:

   Only id required, others optional [OK]

Hint: Only add '!' to required fields in input types [OK]

Common Mistakes:

• Making all fields required
• Forgetting to make id required
• Adding '!' to optional fields