Resource and request objects in Firebase - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a resource object in Firebase?

A resource object represents the data or entity you want to manage or access in Firebase, like a document or a collection.

beginner

What does a request object do in Firebase Cloud Functions?

It carries information about the incoming call, such as parameters, headers, and body data, so the function knows what to process.

intermediate

How do resource and request objects work together in Firebase?

The request object tells the function what resource to act on, and the resource object is the actual data or entity being accessed or changed.

beginner

Give an example of a resource object in Firebase Firestore.

A Firestore document like 'users/user123' is a resource object representing user data stored in the database.

intermediate

Why is understanding request objects important in Firebase Cloud Functions?

Because they let you read what the client sends, so you can respond correctly and securely to actions like reading or writing data.

What does a Firebase request object contain?

A Information about the incoming call like parameters and body

B The entire database content

C Only the user's authentication token

D The Firebase project settings

The request object carries details about the incoming call such as parameters, headers, and body data.

Which of these is an example of a resource object in Firebase?

A A Cloud Function trigger

B A Firestore document like 'users/user123'

C A Firebase project ID

D A request header

A Firestore document represents a resource object, which is the data entity you manage.

How do request and resource objects relate in Firebase Cloud Functions?

A Request tells what to do; resource is what is acted on

B Resource sends data; request stores it

C They are the same thing

D Request is only for authentication

The request object tells the function what to do, and the resource object is the data being accessed or changed.

Why must you read the request object in a Firebase function?

A To change Firebase project settings

B To create a new Firebase project

C To delete the database

D To know what the client wants to do

Reading the request object lets the function understand the client's action and respond properly.

Which Firebase service commonly uses resource and request objects?

A Firebase Analytics

B Firebase Hosting

C Cloud Functions

D Firebase Crashlytics

Cloud Functions use request and resource objects to handle incoming calls and data.

Explain in your own words what resource and request objects are in Firebase and how they work together.

Think about a letter (request) asking to change a file (resource).

Describe a real-life example of a Firebase Cloud Function using request and resource objects.

Imagine a user updating their profile info.

Practice

1. What does a request object in Firebase functions mainly contain?

easy

A. Logs of previous function executions

B. Details about the data or file that triggered the function

C. Settings for Firebase project configuration

D. Information about what the user sent and how

Solution

1. Step 1: Understand the role of request objects

   The request object holds details about the user's input and request method.

2. Step 2: Differentiate from resource objects

   Resource objects describe the trigger data or file, not user input.

3. Final Answer:

   Information about what the user sent and how -> Option D

4. Quick Check:

   Request object = user input info [OK]

Hint: Request = user input details, Resource = trigger data [OK]

Common Mistakes:

• Confusing resource object with request object
• Thinking request holds trigger file info
• Assuming request contains project settings

2. Which of the following is the correct way to access the data sent by a user in a Firebase HTTPS function's request object?

easy

A. request.data.body

B. request.body.data

C. request.payload

D. request.trigger.data

Solution

1. Step 1: Recall request object structure

   In Firebase HTTPS functions, user data is inside request.body.

2. Step 2: Identify correct property for user data

   The user data is accessed as request.body.data if data is nested inside body.

3. Final Answer:

   request.body.data -> Option B

4. Quick Check:

   Access user data via request.body.data [OK]

Hint: User data is inside request.body in HTTPS functions [OK]

Common Mistakes:

• Using request.data.body which is invalid
• Trying to access request.payload which doesn't exist
• Confusing trigger data with request data

3. Given this Firebase function snippet:

exports.myFunction = functions.storage.object().onFinalize((object, context) => {
  console.log(object.name);
  console.log(context.eventId);
});

What does the object parameter represent?

medium

A. The Firebase project configuration

B. The user's HTTP request data

C. The file that triggered the function

D. The function's execution logs

Solution

1. Step 1: Identify the trigger type

   The function triggers on a storage object finalization, meaning a file event.

2. Step 2: Understand the object parameter

   The object parameter holds info about the file that triggered the function.

3. Final Answer:

   The file that triggered the function -> Option C

4. Quick Check:

   Storage trigger object = file info [OK]

Hint: Storage triggers pass file info as object parameter [OK]

Common Mistakes:

• Thinking object is user request data
• Confusing context with resource object
• Assuming object holds config or logs

4. Identify the error in this Firebase HTTPS function code:

exports.func = functions.https.onRequest((resource, request) => {
  console.log(request.body);
});

medium

A. Parameters are reversed; should be (request, response)

B. Missing return statement

C. Incorrect function name

D. No error; code is correct

Solution

1. Step 1: Check HTTPS function parameters

   HTTPS functions receive (request, response) parameters in that order.

2. Step 2: Identify parameter misuse

   The code uses (resource, request) which reverses and misnames parameters.

3. Final Answer:

   Parameters are reversed; should be (request, response) -> Option A

4. Quick Check:

   HTTPS function params = (request, response) [OK]

Hint: HTTPS functions always use (request, response) parameters [OK]

Common Mistakes:

• Swapping request and response parameters
• Using resource parameter in HTTPS function
• Ignoring parameter order importance

5. You want to write a Firebase function triggered by Firestore document changes. Which object should you use to access the changed document's data inside the function?

hard

A. resource.after.data()

B. request.body

C. context.params

D. resource.data()

Solution

1. Step 1: Understand Firestore trigger parameters

   Firestore triggers receive a change object with before and after snapshots.

2. Step 2: Access the new document data

   The updated document data is accessed via change.after.data(), which is the resource object.

3. Final Answer:

   resource.after.data() -> Option A

4. Quick Check:

   Firestore change after data = resource.after.data() [OK]

Hint: Use resource.after.data() for updated Firestore document data [OK]

Common Mistakes:

• Using request.body which is for HTTP functions
• Using context.params which holds path variables
• Using resource.data() which is old snapshot, not updated