Why notifications reach users effectively in Laravel - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to send a notification to a user in Laravel.

Laravel

use App\Notifications\InvoicePaid;

$user->[1](new InvoicePaid($invoice));

Drag options to blanks, or click blank then click option'

Anotify

Balert

CsendNotification

Dmessage

Attempts:

3 left

💡 Hint

Common Mistakes

Using methods like sendNotification or alert which do not exist on the user model.

Trying to call notification methods directly without using the notify method.

In Laravel, the notify method is used on the user model to send notifications.

2fill in blank

medium

Complete the code to define the notification channels in Laravel.

Laravel

public function via($notifiable)
{
    return [[1]];
}

Drag options to blanks, or click blank then click option'

A'mail', 'database'

B['sms', 'push']

C['mail', 'database']

D'sms', 'push'

Attempts:

3 left

💡 Hint

Common Mistakes

Returning a string with commas instead of an array.

Using single quotes without brackets which causes errors.

The via method returns an array of channels as strings inside square brackets.

3fill in blank

hard

Fix the error in the notification class to send an email notification.

Laravel

public function toMail($notifiable)
{
    return (new MailMessage)
        ->subject('Invoice Paid')
        ->[1]('Your invoice has been paid successfully.');
}

Drag options to blanks, or click blank then click option'

Aline

Bmessage

Ccontent

Dtext

Attempts:

3 left

💡 Hint

Common Mistakes

Using message or content which are not valid methods on MailMessage.

Trying to use text which does not exist.

The line method adds a line of text to the email message in Laravel notifications.

4fill in blank

hard

Fill both blanks to store notification data in the database.

Laravel

public function toDatabase($notifiable)
{
    return [
        'invoice_id' => [1],
        'amount' => [2]
    ];
}

Drag options to blanks, or click blank then click option'

A$this->invoice->id

B$this->invoice->total

C$this->invoice->amount

D$this->invoice->number

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong property names like amount instead of total.

Mixing invoice number with invoice id.

Use $this->invoice->id for the invoice ID and $this->invoice->total for the amount to store in the database notification.

5fill in blank

hard

Fill all three blanks to customize the notification's broadcast message.

Laravel

public function toBroadcast($notifiable)
{
    return new BroadcastMessage([
        'invoice_id' => [1],
        'status' => [2],
        'message' => [3]
    ]);
}

Drag options to blanks, or click blank then click option'

A$this->invoice->id

B'paid'

C'Your invoice has been paid successfully.'

D$this->invoice->status

Attempts:

3 left

💡 Hint

Common Mistakes

Using hardcoded status string instead of the invoice status property.

Putting the message in the wrong blank.

Use $this->invoice->id for the invoice ID, $this->invoice->status for the status, and a string message for the broadcast notification.

Practice

1. Why does Laravel use multiple channels like email and database for notifications?

easy

A. Because Laravel requires all notifications to be sent twice

B. To make the code more complex and harder to maintain

C. To ensure notifications reach users through their preferred method

D. To slow down the notification delivery process

Solution

1. Step 1: Understand notification channels in Laravel

   Laravel supports multiple channels like email, SMS, and database to send notifications.

2. Step 2: Reason why multiple channels are useful

   Using multiple channels ensures users get notifications in the way they prefer or can access easily.

3. Final Answer:

   To ensure notifications reach users through their preferred method -> Option C

4. Quick Check:

   Multiple channels = better delivery [OK]

Hint: Multiple channels mean better chances users see notifications [OK]

Common Mistakes:

• Thinking Laravel sends notifications twice by default
• Believing multiple channels slow down delivery
• Assuming complexity is the goal

2. Which of the following is the correct way to send a notification to a user in Laravel?

easy

A. sendNotification($user, 'InvoicePaidNotification');

B. notify($user, new InvoicePaidNotification());

C. Notification::sendUser($user, InvoicePaidNotification);

D. $user->notify(new InvoicePaidNotification());

Solution

1. Step 1: Recall Laravel notification syntax

   Laravel uses the notify method on the user model instance to send notifications.

2. Step 2: Match the correct syntax

   The correct syntax is $user->notify(new NotificationClass()); which matches $user->notify(new InvoicePaidNotification());.

3. Final Answer:

   $user->notify(new InvoicePaidNotification()); -> Option D

4. Quick Check:

   Use notify() method on user [OK]

Hint: Use $user->notify(new NotificationClass()) to send notifications [OK]

Common Mistakes:

• Using global notify() function which doesn't exist
• Calling Notification::sendUser which is invalid
• Passing notification name as string instead of object

3. Given this Laravel notification code snippet:

Notification::send($users, new InvoicePaidNotification());

What happens when this code runs?

medium

A. All users in $users receive the InvoicePaidNotification via their preferred channels

B. Only the first user in $users receives the notification

C. The code throws an error because Notification::send requires a single user

D. Notifications are queued but never sent

Solution

1. Step 1: Understand Notification::send method

   Notification::send accepts a collection or array of users and sends the notification to each.

2. Step 2: Determine behavior of sending notifications

   All users in the $users list receive the notification via their configured channels.

3. Final Answer:

   All users in $users receive the InvoicePaidNotification via their preferred channels -> Option A

4. Quick Check:

   Notification::send sends to all users [OK]

Hint: Notification::send sends to all users in the list [OK]

Common Mistakes:

• Thinking only one user gets notified
• Assuming Notification::send only accepts one user
• Believing notifications are not sent automatically

4. You wrote this code to notify a user:

$user->notify('InvoicePaidNotification');

But the notification is not sent. What is the problem?

medium

A. Notifications require a database channel to work

B. You must pass a notification object, not a string

C. You need to call notify() on Notification facade

D. The notify method only works with arrays

Solution

1. Step 1: Check notify method parameter type

   The notify method expects an instance of a notification class, not a string.

2. Step 2: Identify correct usage

   You should create a new notification object like new InvoicePaidNotification() and pass it.

3. Final Answer:

   You must pass a notification object, not a string -> Option B

4. Quick Check:

   notify() needs notification object [OK]

Hint: Pass new NotificationClass(), not string, to notify() [OK]

Common Mistakes:

• Passing notification class name as string
• Calling notify on Notification facade instead of user
• Assuming database channel is mandatory

5. You want to ensure users receive notifications even if they are offline. Which Laravel feature helps achieve this?

hard

A. Using the database notification channel to store notifications

B. Sending notifications only via email

C. Calling notify() multiple times quickly

D. Using the broadcast channel without queueing

Solution

1. Step 1: Understand offline notification delivery

   Offline users cannot receive real-time notifications but can see stored notifications later.

2. Step 2: Identify Laravel feature for offline delivery

   The database notification channel stores notifications in the database for users to view anytime.

3. Final Answer:

   Using the database notification channel to store notifications -> Option A

4. Quick Check:

   Database channel = offline notification storage [OK]

Hint: Store notifications in database for offline users [OK]

Common Mistakes:

• Thinking email alone ensures offline delivery
• Calling notify() multiple times doesn't help offline users
• Using broadcast without queue misses offline users