Why event-driven architecture decouples code in Laravel - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to dispatch an event in Laravel.

Laravel

<?php

use App\Events\UserRegistered;

function registerUser($user) {
    // Dispatch the event
    event(new [1]($user));
}

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

AUserRegistered

BUserListener

CUserController

DUserModel

Attempts:

3 left

💡 Hint

Common Mistakes

Using a listener or controller class instead of the event class.

Not using the 'new' keyword before the event class.

In Laravel, events are dispatched by creating a new event instance and passing it to the event() helper. Here, UserRegistered is the event class.

2fill in blank

medium

Complete the code to listen for the UserRegistered event in Laravel.

Laravel

<?php

namespace App\Listeners;

use App\Events\UserRegistered;

class SendWelcomeEmail
{
    public function handle([1] $event)
    {
        // Send email logic here
    }
}

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

AUserRegistered

BUserListener

CUserController

DUserModel

Attempts:

3 left

💡 Hint

Common Mistakes

Using the listener class name as the parameter type.

Omitting the type hint.

The listener's handle method receives the event object as a parameter. The type hint must match the event class, here UserRegistered.

3fill in blank

hard

Fix the error in the event listener registration in Laravel's EventServiceProvider.

Laravel

protected $listen = [
    [1]::class => [
        SendWelcomeEmail::class,
    ],
];

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

AUserListener

BUserRegistered

CUserController

DUserModel

Attempts:

3 left

💡 Hint

Common Mistakes

Using the listener class as the key instead of the event class.

Using a controller or model class instead of the event class.

The $listen array maps event classes to their listeners. The key must be the event class, here UserRegistered::class.

4fill in blank

hard

Fill both blanks to create a listener that handles the event and logs a message.

Laravel

<?php

namespace App\Listeners;

use App\Events\UserRegistered;
use Illuminate\Support\Facades\Log;

class LogUserRegistration
{
    public function handle([1] $event)
    {
        Log::[2]('User registered: ' . $event->user->email);
    }
}

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

AUserRegistered

Binfo

Cerror

DUserListener

Attempts:

3 left

💡 Hint

Common Mistakes

Using the listener class as the parameter type.

Using Log::error instead of Log::info for normal logs.

The handle method receives the event object typed as UserRegistered. The Log::info method logs an informational message.

5fill in blank

hard

Fill all three blanks to create an event-driven flow that dispatches an event, listens, and handles it.

Laravel

<?php

// Dispatch event
function registerUser($user) {
    event(new [1]($user));
}

// Listener handle method
class SendNotification
{
    public function handle([2] $event)
    {
        // Notify user
        notify($event->user);
    }
}

// EventServiceProvider mapping
protected $listen = [
    [3]::class => [
        SendNotification::class,
    ],
];

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

AUserRegistered

DUserListener

Attempts:

3 left

💡 Hint

Common Mistakes

Using different class names in dispatch, handle, and mapping.

Using listener class name instead of event class.

All blanks require the event class UserRegistered to correctly connect dispatching, listening, and mapping in Laravel's event-driven architecture.