Nested objects and arrays in Firebase - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a nested object in Firebase Firestore?

A nested object is an object stored inside another object as a field. It helps organize related data together within a document.

beginner

How are arrays used in Firebase Firestore documents?

Arrays store multiple values in a single field. They can hold strings, numbers, objects, or even nested arrays.

intermediate

How do you update a nested object field in Firestore without overwriting the whole object?

Use dot notation in the update method to target specific nested fields, so only those fields change, not the entire object.

intermediate

Can arrays in Firestore contain nested objects?

Yes, arrays can contain objects, and those objects can themselves have nested fields, allowing complex data structures.

advanced

What is a best practice when designing nested data in Firestore?

Keep nested objects and arrays simple and avoid deeply nested structures to maintain easy querying and performance.

In Firestore, how do you access a nested field called 'address.city' inside a document?

A Use 'address.city' with dot notation

B Use 'address_city' as a single field

C Use 'address[city]' with brackets

D You cannot access nested fields

Dot notation like 'address.city' is used to access nested fields in Firestore documents.

Which data type can Firestore arrays NOT contain?

A Strings

B Numbers

C Functions

D Objects

Firestore arrays can contain strings, numbers, and objects but cannot store functions.

What happens if you update a nested object field without dot notation?

A Only the nested field updates

B The entire nested object is overwritten

C Firestore throws an error

D Nothing changes

Without dot notation, updating a nested object field overwrites the whole nested object.

Is it possible to have an array inside a nested object in Firestore?

A Yes, arrays can be inside nested objects

B No, arrays must be top-level fields

C Only if the array is empty

D Only if the nested object is empty

Firestore supports arrays inside nested objects, allowing flexible data structures.

Why should you avoid deeply nested objects in Firestore?

A Firestore does not support nested objects

B They are automatically flattened

C They cost more money

D They increase query complexity and reduce performance

Deeply nested objects make queries complex and can slow down performance.

Explain how nested objects and arrays work in Firebase Firestore and why they are useful.

Think about how you store related information inside a single document.

Describe best practices for updating nested fields in Firestore without overwriting entire objects.

Focus on how to change only what you want inside nested data.

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