Mailable classes in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this Mailable's build method?

Consider this Laravel Mailable class. What will be the subject of the email when this Mailable is sent?

Laravel

class WelcomeMail extends Mailable {
    public function build() {
        return $this->subject('Welcome!')->view('emails.welcome');
    }
}

$mail = new WelcomeMail();
$subject = $mail->build()->subject;

A Throws an error because subject is not accessible

B null

C 'emails.welcome'

D 'Welcome!'

💡 Hint

Remember how Laravel's Mailable class handles chaining and property access.

The `subject()` method sets the `$subject` property (publicly accessible dynamic property) and returns `$this`. `build()` chains this and returns the instance, so `$mail->build()->subject` returns `'Welcome!'`.

❓ state_output

intermediate

What data is available in the email view?

Given this Mailable class, what variables will be available inside the Blade view 'emails.order'?

Laravel

class OrderShipped extends Mailable {
    public $order;

    public function __construct($order) {
        $this->order = $order;
    }

    public function build() {
        return $this->view('emails.order');
    }
}

$order = ['id' => 123, 'total' => 49.99];
$mail = new OrderShipped($order);

A A variable named $order containing the array ['id' => 123, 'total' => 49.99]

B No variables are available in the view

C A variable named $data containing the order array

D Only public methods of the Mailable are available, no variables

💡 Hint

Public properties of the Mailable are automatically passed to the view.

Laravel automatically makes all public properties of the Mailable class available as variables in the email view. Here, $order is public, so it is accessible in the Blade template.

📝 Syntax

advanced

Which option correctly queues this Mailable?

You want to send the Mailable asynchronously using Laravel's queue system. Which code snippet correctly queues the Mailable?

Laravel

class NotificationMail extends Mailable {
    public function build() {
        return $this->view('emails.notify');
    }
}

// Assume $user is a valid User model instance

A Mail::to($user)->queue(new NotificationMail());

B NotificationMail::queue($user);

C Mail::to($user)->send(new NotificationMail());

D NotificationMail::sendQueued($user);

💡 Hint

Check Laravel's Mail facade methods for queuing emails.

The Mail facade has a queue() method to send mail asynchronously. Option A correctly uses Mail::to()->queue() with a new Mailable instance.

🔧 Debug

advanced

Why does this Mailable fail to send with an error about missing view?

This Mailable class throws an error when sending: "View [emails.invoice] not found." What is the most likely cause?

Laravel

class InvoiceMail extends Mailable {
    public function build() {
        return $this->view('emails.invoice');
    }
}

Mail::to('[e-mail]')->send(new InvoiceMail());

A The Mailable class is missing the subject() method

B The Blade view file 'emails/invoice.blade.php' does not exist in the resources/views directory

C The Mail facade is not imported correctly

D The email address is invalid

💡 Hint

Check the file path and name of the Blade template.

Laravel looks for the Blade view file at resources/views/emails/invoice.blade.php. If this file is missing, it throws a 'View not found' error.

🧠 Conceptual

expert

What happens if you call build() twice on the same Mailable instance?

Consider this code snippet. What will be the result of calling build() twice on the same Mailable object?

Laravel

class AlertMail extends Mailable {
    public function build() {
        return $this->subject('Alert')->view('emails.alert');
    }
}

$mail = new AlertMail();
$first = $mail->build();
$second = $mail->build();

$subjectFirst = $first->subject;
$subjectSecond = $second->subject;

A Both $subjectFirst and $subjectSecond are null because subject is not accessible

B $subjectFirst is 'Alert' but $subjectSecond is null

C $subjectFirst and $subjectSecond both equal 'Alert'

D Calling build() twice causes an error because the Mailable can only be built once

💡 Hint

Remember what build() returns and how subject() works internally.

`build()` returns `$this` each time and can be called multiple times. `subject()` sets the publicly accessible `$subject` property each call. `$first` and `$second` reference the same instance, so both access `'Alert'`.