Type definitions in GraphQL - Step-by-Step Execution

Concept Flow - Type definitions

Start schema

↓

Define types

↓

Add fields with types

↓

Use scalar or custom types

↓

Schema ready for queries/mutations

GraphQL type definitions start by defining types, then adding fields with scalar or custom types, preparing the schema for queries and mutations.

Execution Sample

GraphQL

type Book {
  id: ID!
  title: String!
  author: Author
}

type Author {
  id: ID!
  name: String!
}

Defines two types, Book and Author, with fields and their types, including required fields using !.

Execution Table

Step	Action	Type/Field	Type Assigned	Notes
1	Define type	Book	Object Type	Start defining Book type
2	Add field	id	ID!	Unique identifier, required
3	Add field	title	String!	Book title, required
4	Add field	author	Author	Reference to Author type, optional
5	Define type	Author	Object Type	Start defining Author type
6	Add field	id	ID!	Unique identifier, required
7	Add field	name	String!	Author name, required
8	Schema complete	-	-	Types ready for queries and mutations

💡 All types and fields defined with their types; schema is ready for use.

Variable Tracker

Type/Field	Start	After Step 1	After Step 4	After Step 7	Final
Book	undefined	Object Type defined	Fields: id(ID!), title(String!), author(Author)	Fields unchanged	Complete
Author	undefined	undefined	undefined	Object Type defined with fields id(ID!), name(String!)	Complete

Key Moments - 2 Insights

Why does the exclamation mark (!) appear after some types?

The exclamation mark means the field is required (non-null). See execution_table rows 2, 3, 6, and 7 where fields have ! indicating they must have a value.

Can a field reference another type?

Yes, fields can reference other types as in row 4 where 'author' field in Book references the Author type.

Visual Quiz - 3 Questions

Look at the execution_table, what type is assigned to the 'title' field in the Book type?

A ID!

B String!

C Author

D String

💡 Hint

Check execution_table row 3 under 'Type Assigned' column.

At which step is the Author type fully defined with its fields?

A Step 7

B Step 6

C Step 4

D Step 8

💡 Hint

Look at execution_table rows 5 to 7 for Author type field additions.

If the 'author' field in Book was marked as 'Author!' instead of 'Author', what would that mean?

A The author field is a scalar type

B The author field is optional

C The author field is required (non-null)

D The author field is a list

💡 Hint

Recall the meaning of ! from key_moments and execution_table rows 2 and 3.

Concept Snapshot

GraphQL type definitions:
- Use 'type TypeName { fields }' to define types
- Fields have 'name: Type' format
- '!' means field is required (non-null)
- Fields can reference scalar or custom types
- Types form schema for queries and mutations

Full Transcript

This visual execution traces how GraphQL type definitions are built step-by-step. We start by defining a type named Book, then add fields like id with type ID! meaning required unique identifier, title as required String, and author referencing another type Author. Next, we define Author type with id and name fields, both required. The exclamation mark means the field cannot be null. Fields can reference other types, allowing nested data structures. After all fields are added, the schema is ready for queries and mutations. The execution table shows each step, the variable tracker shows how types and fields build up. Key moments clarify common confusions about required fields and type references. The quiz tests understanding of field types, definition steps, and meaning of required fields. This helps beginners see how GraphQL schemas are constructed visually and clearly.