Object types in GraphQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an Object type in GraphQL?

An Object type in GraphQL defines a set of fields that represent the shape of data you can query. It acts like a blueprint for the data structure.

beginner

How do you define fields inside an Object type in GraphQL?

Fields inside an Object type are defined by specifying the field name followed by its type, for example: name: String or age: Int.

intermediate

Can Object types in GraphQL have fields that are other Object types?

Yes, fields in an Object type can reference other Object types, allowing nested data structures and relationships between data.

beginner

What is the difference between a scalar type and an Object type in GraphQL?

Scalar types represent basic data like strings or numbers, while Object types represent complex data structures made of multiple fields.

beginner

Why are Object types important in GraphQL schemas?

Object types define the shape of the data clients can request, making the API clear and predictable. They help organize data and enable powerful queries.

What does an Object type in GraphQL represent?

A A set of fields describing data structure

B A single scalar value like a string

C A function to fetch data

D A database table

An Object type defines a group of fields that describe the shape of data you can query.

Which of these is a valid field definition inside a GraphQL Object type?

A name: String

B name = String

C String: name

D field name String

Fields are defined as fieldName: Type in GraphQL Object types.

Can a field in a GraphQL Object type be another Object type?

A No

B Yes

C Only if it is a scalar

D Only in mutations

Fields can be other Object types, allowing nested data structures.

Which of the following is NOT a scalar type in GraphQL?

A Boolean

B String

C Int

D User

User is typically an Object type, not a scalar.

Why do GraphQL schemas use Object types?

A To write server-side code

B To store data in the database

C To define the shape of data clients can request

D To style the UI

Object types define the data structure clients can query, making APIs clear and organized.

Explain what an Object type is in GraphQL and why it is useful.

Think about how you describe a person with name, age, and address fields.

Describe how fields are defined inside a GraphQL Object type and how they can relate to other Object types.

Imagine a book object with an author field that is another object.

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