Nested objects and arrays in Firebase - Commands & Configuration

Introduction

Sometimes you want to store complex data like lists or groups inside your database. Nested objects and arrays let you keep related information together in one place, making it easier to organize and find later.

When you want to save a user's profile with multiple addresses inside one record.

When you need to store a list of items someone bought in a single order.

When you want to keep comments and replies grouped under a post.

When you want to save settings that have multiple options inside one document.

When you want to store a collection of tags or labels for an article.

Commands

This command saves a user document with nested objects and arrays: the contacts object has an email and a list of phone numbers.

Terminal

firebase firestore:documents:set users/user123 '{"name": "Alice", "contacts": {"email": "[e-mail]", "phones": ["123-4567", "987-6543"]}}'

Expected Output

✔  Document users/user123 has been created or overwritten.

→

--merge - To add or update fields without overwriting the whole document

This command retrieves the user document to check that the nested objects and arrays were saved correctly.

Terminal

firebase firestore:documents:get users/user123

Expected Output

{

  "name": "Alice",

  "contacts": {

    "email": "[e-mail]",

    "phones": [

      "123-4567",

      "987-6543"

    ]

  }

}

This command updates the phones array inside the nested contacts object without changing other fields.

Terminal

firebase firestore:documents:update users/user123 '{"contacts.phones": ["111-2222", "333-4444"]}'

Expected Output

✔  Document users/user123 has been updated.

Retrieve the document again to confirm the phones array was updated inside the nested object.

Terminal

firebase firestore:documents:get users/user123

Expected Output

{

  "name": "Alice",

  "contacts": {

    "email": "[e-mail]",

    "phones": [

      "111-2222",

      "333-4444"

    ]

  }

}

Key Concept

If you remember nothing else from this pattern, remember: nested objects and arrays let you group related data inside one document for easier access and updates.

Common Mistakes

Trying to update a nested field without using dot notation.

The update command treats the whole field as a string key, so it overwrites the nested object instead of just the inner field.

Use dot notation like 'contacts.phones' to update only the nested array inside the object.

Passing nested data as a string without proper JSON format.

Firebase commands expect valid JSON; incorrect formatting causes errors or wrong data storage.

Always use valid JSON with double quotes and proper brackets for objects and arrays.

Summary

Use nested objects and arrays to store complex related data inside one document.

Use dot notation to update nested fields without overwriting the whole object.

Always check your data with get commands to confirm the structure is correct.

Practice

1. What is the main purpose of using nested objects in Firebase documents?

easy

A. To create separate databases within Firebase

B. To group related data inside one document for better organization

C. To store multiple documents in a collection

D. To encrypt data automatically

Solution

1. Step 1: Understand nested objects concept

   Nested objects allow grouping related data inside a single document, making it easier to manage.

2. Step 2: Compare with other options

   Options A, B, and D describe different Firebase features unrelated to nested objects.

3. Final Answer:

   To group related data inside one document for better organization -> Option B

4. Quick Check:

   Nested objects = group related data [OK]

Hint: Nested objects group related data inside one document [OK]

Common Mistakes:

• Confusing nested objects with collections
• Thinking nested objects create separate databases
• Assuming nested objects encrypt data

2. Which of the following is the correct way to define an array inside a Firebase document?

easy

A. "tags": ["firebase", "cloud"]

B. "tags": {"0": "firebase", "1": "cloud"}

C. "tags": "firebase, cloud"

D. "tags": {"firebase", "cloud"}

Solution

1. Step 1: Identify correct array syntax in Firebase

   Arrays in Firebase are defined using square brackets with comma-separated values.

2. Step 2: Evaluate each option

   "tags": ["firebase", "cloud"] uses square brackets correctly. Options A and D use curly braces which define objects, not arrays. "tags": "firebase, cloud" is a string, not an array.

3. Final Answer:

   "tags": ["firebase", "cloud"] -> Option A

4. Quick Check:

   Arrays use square brackets [] [OK]

Hint: Arrays use square brackets [] in Firebase [OK]

Common Mistakes:

• Using curly braces {} instead of square brackets []
• Writing arrays as comma-separated strings
• Confusing objects with arrays

3. Given this Firebase document snippet:

{"user": {"name": "Anna", "roles": ["admin", "editor"]}}

What will be the value of user.roles[1]?

medium

A. "admin"

B. undefined

C. "editor"

D. "user"

Solution

1. Step 1: Understand array indexing in Firebase data

   Arrays start at index 0, so roles[0] is "admin" and roles[1] is "editor".

2. Step 2: Identify the value at index 1

   The second element (index 1) in the roles array is "editor".

3. Final Answer:

   "editor" -> Option C

4. Quick Check:

   Index 1 in roles array = "editor" [OK]

Hint: Array indexes start at 0; roles[1] is second item [OK]

Common Mistakes:

• Assuming array indexes start at 1
• Confusing object keys with array indexes
• Thinking roles[1] is undefined

4. You have this Firebase document:

{"profile": {"contacts": {"email": "[e-mail]", "phones": ["123-456", "789-012"]}}}

Which code snippet correctly accesses the second phone number?

medium

A. profile[contacts].phones[1]

B. profile.contacts.phones[2]

C. profile.contacts[phones][1]

D. profile.contacts.phones[1]

Solution

1. Step 1: Understand correct dot and bracket notation

   Access nested objects with dots and arrays with brackets. Index 1 is second item.

2. Step 2: Evaluate each option

   profile.contacts.phones[1] uses correct dot notation and index 1. profile.contacts.phones[2] uses index 2 which is out of range. Options C and D misuse bracket notation for keys.

3. Final Answer:

   profile.contacts.phones[1] -> Option D

4. Quick Check:

   Use dot for keys, brackets for array index [OK]

Hint: Use dot notation for keys, brackets for array index [OK]

Common Mistakes:

• Using wrong array index (2 instead of 1)
• Using brackets incorrectly for object keys
• Mixing quotes and brackets wrongly

5. You want to store a list of users where each user has a name and a list of favorite colors. Which Firebase structure correctly uses nested objects and arrays?

hard

A. {"users": [{"name": "Tom", "favorites": ["red", "blue"]}, {"name": "Sue", "favorites": ["green"]}]}

B. {"users": {"Tom": "red, blue", "Sue": "green"}}

C. {"users": [{"name": "Tom", "favorites": "red, blue"}, {"name": "Sue", "favorites": "green"}]}

D. {"users": ["Tom", "Sue"], "favorites": ["red", "blue", "green"]}

Solution

1. Step 1: Identify correct nested structure for users and their favorite colors

   Each user should be an object with a name and an array of favorite colors.

2. Step 2: Evaluate each option

   {"users": [{"name": "Tom", "favorites": ["red", "blue"]}, {"name": "Sue", "favorites": ["green"]}]} correctly nests user objects with arrays for favorites. {"users": {"Tom": "red, blue", "Sue": "green"}} uses a string instead of array. {"users": [{"name": "Tom", "favorites": "red, blue"}, {"name": "Sue", "favorites": "green"}]} uses strings for favorites, not arrays. {"users": ["Tom", "Sue"], "favorites": ["red", "blue", "green"]} separates users and favorites incorrectly.

3. Final Answer:

   {"users": [{"name": "Tom", "favorites": ["red", "blue"]}, {"name": "Sue", "favorites": ["green"]}]} -> Option A

4. Quick Check:

   Nested objects with arrays for lists = {"users": [{"name": "Tom", "favorites": ["red", "blue"]}, {"name": "Sue", "favorites": ["green"]}]} [OK]

Hint: Use objects for users, arrays for lists inside them [OK]

Common Mistakes:

• Using strings instead of arrays for lists
• Separating users and favorites incorrectly
• Not nesting favorites inside each user object