Creating listeners in Laravel - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a listener class in Laravel.

Laravel

class UserRegisteredListener {
    public function [1]($event) {
        // handle the event
    }
}

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

Alisten

Bhandle

Cfire

Dtrigger

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'listen' or 'fire' instead of 'handle' as the method name.

The handle method is the standard method Laravel calls when the event is fired.

2fill in blank

medium

Complete the code to register a listener for an event in Laravel's EventServiceProvider.

Laravel

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

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

AUserRegisteredListener

BUserRegisteredEvent

CUserRegisteredHandler

DUserRegisteredSubscriber

Attempts:

3 left

💡 Hint

Common Mistakes

Using the event class name instead of the listener class.

Using 'Subscriber' when the question is about listeners.

The listener class name should be listed here to handle the event.

3fill in blank

hard

Fix the error in the listener method signature to properly receive the event.

Laravel

public function handle([1] $event) {
    // process event
}

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

AUserRegistered

BUserRegisteredListener

CEvent

DListener

Attempts:

3 left

💡 Hint

Common Mistakes

Using the listener class as the parameter type.

Using a generic 'Event' class without importing it.

The listener's handle method must type hint the event class it listens to.

4fill in blank

hard

Fill both blanks to dispatch an event and listen to it with a listener.

Laravel

event(new [1]($user));

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

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

AUserRegistered

BUserLoggedIn

DUserLoggedOut

Attempts:

3 left

💡 Hint

Common Mistakes

Using different event names for dispatching and listening.

Confusing login and registration events.

The event dispatched and the event listened to must be the same class.

5fill in blank

hard

Fill all three blanks to create a listener class that handles an event and logs a message.

Laravel

use Illuminate\Support\Facades\Log;

class [1] {
    public function handle([2] $event) {
        Log::info('[3] event handled');
    }
}

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

AUserRegisteredListener

BUserRegistered

DUserLoggedIn

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatching event names in the handle method and log message.

Using the wrong class name for the listener.

The listener class name, the event type in the handle method, and the event name in the log message must correspond.

Practice

1. What is the main purpose of creating listeners in Laravel?

easy

A. To define database migrations

B. To respond automatically when specific events happen

C. To create routes for web requests

D. To handle user authentication manually

Solution

1. Step 1: Understand what listeners do

   Listeners are designed to respond automatically when events occur in the application.

2. Step 2: Compare with other options

   Options B, C, and D relate to migrations, routing, and authentication, which are not the main purpose of listeners.

3. Final Answer:

   To respond automatically when specific events happen -> Option B

4. Quick Check:

   Listeners respond to events = A [OK]

Hint: Listeners react to events automatically in Laravel [OK]

Common Mistakes:

• Confusing listeners with routes or migrations
• Thinking listeners handle authentication directly
• Believing listeners are manually triggered

2. Which of the following is the correct artisan command to create a listener named UserRegisteredListener?

easy

A. php artisan create:listener UserRegisteredListener

B. php artisan make:event UserRegisteredListener

C. php artisan listener:create UserRegisteredListener

D. php artisan make:listener UserRegisteredListener

Solution

1. Step 1: Recall the artisan command for listeners

   The correct command to create a listener is php artisan make:listener ListenerName.

2. Step 2: Check other options

   Options A and C use incorrect command formats, and D creates an event, not a listener.

3. Final Answer:

   php artisan make:listener UserRegisteredListener -> Option D

4. Quick Check:

   Use make:listener to create listeners [OK]

Hint: Use 'make:listener' to create listeners with artisan [OK]

Common Mistakes:

• Using 'create:listener' instead of 'make:listener'
• Confusing listener creation with event creation
• Typing commands in wrong order

3. Given this listener code snippet, what will be the output when the event triggers?

public function handle(UserRegistered $event) {
    echo 'Welcome, ' . $event->user->name . '!';
}

medium

A. It does nothing because echo is not allowed in listeners

B. It throws an error because $event is undefined

C. It prints 'Welcome, ' followed by the user's name

D. It prints 'Welcome, User!' regardless of the actual name

Solution

1. Step 1: Understand the handle method

   The handle method receives the event object, here UserRegistered, which contains the user data.

2. Step 2: Analyze the echo statement

   It prints 'Welcome, ' plus the user's name from the event object, so the output is personalized.

3. Final Answer:

   It prints 'Welcome, ' followed by the user's name -> Option C

4. Quick Check:

   handle() prints welcome message with user name [OK]

Hint: handle() uses event data to customize output [OK]

Common Mistakes:

• Assuming $event is not passed automatically
• Thinking echo is disallowed in listeners
• Ignoring the user property inside the event

4. Identify the error in this listener class code:

class SendNotification {
    public function handle() {
        // send notification code
    }
}

medium

A. The handle method must accept the event object as a parameter

B. The class name must end with 'Listener'

C. The handle method should be static

D. Listeners cannot send notifications

Solution

1. Step 1: Check handle method signature

   The handle method must accept the event object parameter to receive event data.

2. Step 2: Verify other options

   Class name ending with 'Listener' is a convention but not required; handle should not be static; listeners can send notifications.

3. Final Answer:

   The handle method must accept the event object as a parameter -> Option A

4. Quick Check:

   handle(event) needs event parameter [OK]

Hint: handle() always needs event parameter [OK]

Common Mistakes:

• Omitting event parameter in handle method
• Thinking class name must have 'Listener' suffix
• Making handle method static incorrectly

5. You want to create a listener that logs a message only when a user registers and their email ends with '@example.com'. How should you modify the listener's handle method to achieve this?

hard

A. Add an if condition inside handle to check $event->user->email ends with '@example.com' before logging

B. Create a separate listener for '@example.com' emails and register it separately

C. Modify the event to only fire for '@example.com' emails

D. Use middleware to filter events before listeners run

Solution

1. Step 1: Understand listener filtering

   Listeners receive all events they listen to; filtering specific cases is done inside the handle method.

2. Step 2: Apply condition inside handle

   Check if the user's email ends with '@example.com' using an if statement before running the logging code.

3. Step 3: Evaluate other options

   Creating separate listeners or modifying events is more complex; middleware does not filter events.

4. Final Answer:

   Add an if condition inside handle to check $event->user->email ends with '@example.com' before logging -> Option A

5. Quick Check:

   Filter event data inside handle() with if condition [OK]

Hint: Filter event data inside handle() using if condition [OK]

Common Mistakes:

• Trying to filter events outside listener handle method
• Assuming middleware filters events
• Creating unnecessary multiple listeners