Object types in GraphQL - Step-by-Step Execution

Concept Flow - Object types

Define Object Type

↓

Specify Fields & Types

↓

Use Object Type in Queries/Mutations

↓

Request Data Matching Object Type

↓

Receive Structured Response

This flow shows how you define an object type, specify its fields, use it in queries, and get structured data back.

Execution Sample

GraphQL

type Book {
  title: String
  author: String
  pages: Int
}

query {
  book {
    title
    author
  }
}

Defines a Book object type and queries for its title and author fields.

Execution Table

Step	Action	Evaluation	Result
1	Define object type Book with fields title, author, pages	Schema updated	Book type ready
2	Send query requesting book { title, author }	Query parsed	Fields title and author selected
3	Resolve book field	Fetch book data	{ title: "1984", author: "George Orwell", pages: 328 }
4	Return only requested fields	Filter fields	{ title: "1984", author: "George Orwell" }
5	Send response to client	Response ready	{ "data": { "book": { "title": "1984", "author": "George Orwell" } } }
6	End	Query complete	Execution stops

💡 Query completed and response sent to client

Variable Tracker

Variable	Start	After Step 3	After Step 4	Final
bookData	undefined	{ title: "1984", author: "George Orwell", pages: 328 }	{ title: "1984", author: "George Orwell" }	{ title: "1984", author: "George Orwell" }

Key Moments - 2 Insights

Why does the response only include title and author, not pages?

Because the query only requested title and author fields (see execution_table step 4), GraphQL returns only those fields.

What happens if a field is missing in the object type definition?

GraphQL will not allow querying that field; it must be defined in the object type schema (see execution_table step 1).

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of bookData after step 3?

A { title: "1984", author: "George Orwell", pages: 328 }

B { title: "1984", author: "George Orwell" }

C undefined

D { title: "1984" }

💡 Hint

Check the 'bookData' row in variable_tracker after Step 3

At which step does GraphQL filter the fields to only those requested?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look at the 'Action' column in execution_table for filtering fields

If the query requested the pages field, how would the final response change?

A It would exclude pages

B It would cause an error

C It would include pages with value 328

D It would return pages as null

💡 Hint

Refer to how requested fields control response content in execution_table steps 4 and 5

Concept Snapshot

GraphQL Object Types:
- Define with 'type' keyword and fields
- Fields have names and types (String, Int, etc.)
- Queries request specific fields
- Response includes only requested fields
- Enables precise, structured data fetching

Full Transcript

This visual execution shows how GraphQL object types work. First, you define an object type with fields and their types. Then, you write a query requesting specific fields from that object. When the query runs, GraphQL fetches the full object data but returns only the fields requested. This keeps responses efficient and structured. The example uses a Book type with title, author, and pages fields. The query asks for title and author, so the response includes only those. This step-by-step trace helps beginners see how object types shape queries and responses.

Practice

1. What is the main purpose of an Object type in GraphQL?

easy

A. To execute database queries directly

B. To create user interface components

C. To store data permanently

D. To define the shape and fields of data objects

Solution

1. Step 1: Understand the role of Object types in GraphQL

   Object types describe what fields an object has and their types, shaping the data structure.

2. Step 2: Differentiate from other concepts

   Object types do not execute queries, store data, or create UI components; they only define data shapes.

3. Final Answer:

   To define the shape and fields of data objects -> Option D

4. Quick Check:

   Object type = data shape definition [OK]

Hint: Object types describe data fields and their types [OK]

Common Mistakes:

• Confusing object types with query execution
• Thinking object types store data
• Mixing object types with UI components

2. Which of the following is the correct syntax to define a GraphQL object type named Book with a title field of type String?

easy

A. object Book { title: String }

B. type Book { title: String }

C. Book type { title: String }

D. define Book { title: String }

Solution

1. Step 1: Recall GraphQL object type syntax

   GraphQL uses the keyword type followed by the name and fields in braces.

2. Step 2: Check each option

   Only type Book { title: String } uses the correct syntax: type Book { title: String }. Others use invalid keywords.

3. Final Answer:

   type Book { title: String } -> Option B

4. Quick Check:

   Keyword 'type' + name + fields = correct syntax [OK]

Hint: Use 'type' keyword to define object types [OK]

Common Mistakes:

• Using 'object' or 'define' instead of 'type'
• Placing type name after 'type' incorrectly
• Missing braces around fields

3. Given the GraphQL object type definition:

type User {
  id: ID
  name: String
  age: Int
}

What is the expected result of querying:

{ user { id name } }

?

medium

A. Returns user object with only id and name fields

B. Returns user object with id, name, and age fields

C. Returns an error because age is missing

D. Returns null because query is incomplete

Solution

1. Step 1: Understand GraphQL query field selection

   GraphQL returns only the fields requested in the query, here id and name.

2. Step 2: Check if missing fields cause errors

   Missing age in query does not cause error; it is simply not returned.

3. Final Answer:

   Returns user object with only id and name fields -> Option A

4. Quick Check:

   Query fields = returned fields only [OK]

Hint: GraphQL returns only requested fields in query [OK]

Common Mistakes:

• Expecting all fields to be returned by default
• Thinking missing fields cause errors
• Assuming incomplete queries return null

4. Identify the error in this GraphQL object type definition:

type Product {
  id: ID!
  name: String
  price: Float
  price: Int
}

medium

A. ID type cannot have exclamation mark

B. Missing exclamation mark on 'name' field

C. Duplicate field name 'price' with different types

D. Object type must have at least one field

Solution

1. Step 1: Review field names and types

   The field price is declared twice with different types (Float and Int), which is invalid.

2. Step 2: Check other options

   Exclamation mark on ID! is valid for non-null. Fields can be optional. Object type can have multiple fields.

3. Final Answer:

   Duplicate field name 'price' with different types -> Option C

4. Quick Check:

   Field names must be unique in object type [OK]

Hint: Field names must be unique in object types [OK]

Common Mistakes:

• Allowing duplicate field names
• Misunderstanding non-null syntax
• Thinking object types need all fields non-null

5. You want to define a GraphQL object type Author that includes a list of Book objects. Which is the correct way to define the books field?

hard

A. books: [Book]

B. books: Book[]

C. books: List<Book>

D. books: {Book}

Solution

1. Step 1: Recall GraphQL list syntax

   GraphQL uses square brackets around a type to indicate a list, e.g., [Book].

2. Step 2: Evaluate each option

   books: [Book] uses correct GraphQL syntax. Options A, B, and C use syntax from other languages or invalid formats.

3. Final Answer:

   books: [Book] -> Option A

4. Quick Check:

   Lists use square brackets in GraphQL [OK]

Hint: Use square brackets for lists in GraphQL types [OK]

Common Mistakes:

• Using array syntax from other languages
• Using curly braces instead of brackets
• Confusing list syntax with generics