Schema definition in GraphQL - Step-by-Step Execution

Concept Flow - Schema definition

Start Schema

↓

Define Types

↓

Add Fields to Types

↓

Specify Field Types

↓

Add Queries/Mutations

↓

Schema Ready for Use

The schema definition starts by defining types, adding fields with their types, then adding queries or mutations, resulting in a complete schema.

Execution Sample

GraphQL

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

type Query {
  books: [Book]
}

Defines a Book type with fields and a Query type to fetch books.

Execution Table

Step	Action	Definition Added	Resulting Schema Part
1	Define type Book	type Book { id: ID!, title: String!, author: String }	Book type with 3 fields
2	Define type Query	type Query { books: [Book] }	Query type with books field returning list of Book
3	Schema complete	All types and fields defined	Schema ready to use for queries

💡 All types and fields defined, schema is complete

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
Schema	empty	Book type defined	Book and Query types defined	Complete schema with Book and Query

Key Moments - 3 Insights

Why do we need to specify field types like String or ID?

Field types tell GraphQL what kind of data to expect; see execution_table step 1 where fields have types like ID! and String!

What does the exclamation mark (!) mean after a type?

It means the field is required (non-nullable), as shown in execution_table step 1 for id and title fields.

Why is the Query type important?

Query defines how clients can ask for data; in execution_table step 2, books field allows fetching Book list.

Visual Quiz - 3 Questions

Look at the execution_table, what is defined in Step 1?

A The Query type with books field

B The Book type with id, title, author fields

C The Mutation type

D The schema is complete

💡 Hint

Check execution_table row for Step 1 under 'Definition Added'

At which step is the Query type added to the schema?

A Step 1

B Step 3

C Step 2

D Query type is not added

💡 Hint

Look at execution_table row for Step 2

If we remove the exclamation mark from 'id: ID!' in Book type, what changes?

A id becomes optional (nullable)

B id becomes a list

C id becomes a mutation

D No change

💡 Hint

Refer to key_moments about exclamation mark meaning

Concept Snapshot

Schema definition in GraphQL:
- Define types with 'type TypeName { fields }'
- Fields have names and types (e.g., String, ID)
- '!' means field is required
- Query type defines how to fetch data
- Schema combines types and queries for API structure

Full Transcript

Schema definition in GraphQL involves creating types that describe the shape of data. Each type has fields with specific data types, such as String or ID. An exclamation mark after a type means the field is required and cannot be null. The Query type is special because it defines how clients can request data from the API. The schema is complete when all types and queries are defined, ready for use in fetching or modifying data.