Event subscribers in Laravel - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to register an event subscriber class in Laravel's EventServiceProvider.

Laravel

protected $subscribe = [[1]::class];

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

AUserEventHandler

BUserEventListener

CUserEventSubscriber

DUserEventObserver

Attempts:

3 left

💡 Hint

Common Mistakes

Using event listener class names instead of subscriber class names.

Forgetting to add ::class after the class name.

In Laravel, event subscribers are registered by listing their class names in the $subscribe array in the EventServiceProvider.

2fill in blank

medium

Complete the method name in the subscriber class to listen for the UserRegistered event.

Laravel

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

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

AsubscribeUserRegistered

BonUserRegistered

ClistenUserRegistered

DhandleUserRegistered

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'handle' prefix which is common in listeners but not subscribers.

Using 'subscribe' which is not a method name for handling events.

Subscriber methods that handle events usually start with 'on' followed by the event name in Laravel.

3fill in blank

hard

Fix the error in the subscriber's subscribe method to register the event handler.

Laravel

public function subscribe(Dispatcher $events) {
    $events->listen(
        UserRegistered::class, 
        [[1]::class, 'onUserRegistered']
    );
}

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

AUserEventListener

BUserRegisteredListener

CUserRegisteredHandler

DUserEventSubscriber

Attempts:

3 left

💡 Hint

Common Mistakes

Using listener or handler class names instead of the subscriber class.

Passing the event class instead of the subscriber class.

The subscriber class itself is passed as the first element in the listener array to register the handler method.

4fill in blank

hard

Fill both blanks to define the subscribe method and register two event handlers in the subscriber class.

Laravel

public function subscribe(Dispatcher $events) {
    $events->listen(UserRegistered::class, [[1]::class, 'onUserRegistered']);
    $events->listen(UserLoggedIn::class, [[2]::class, 'onUserLoggedIn']);
}

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

AUserEventSubscriber

BUserEventListener

CUserSubscriber

DUserEventHandler

Attempts:

3 left

💡 Hint

Common Mistakes

Using different class names for each event handler.

Using listener or handler class names instead of subscriber class.

Both event handlers are methods inside the same subscriber class, so the class name is repeated.

5fill in blank

hard

Fill all three blanks to create a subscriber class with the subscribe method registering handlers for three events.

Laravel

class UserEventSubscriber {
    public function subscribe(Dispatcher $events) {
        $events->listen(UserRegistered::class, [[1]::class, 'onUserRegistered']);
        $events->listen(UserLoggedIn::class, [[2]::class, 'onUserLoggedIn']);
        $events->listen(UserLoggedOut::class, [[3]::class, 'onUserLoggedOut']);
    }
}

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

AUserEventSubscriber

BUserEventListener

CUserSubscriber

DUserEventHandler

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing different class names for event handlers.

Using listener or handler class names instead of subscriber class.

The subscriber class registers all event handlers using its own class name in the subscribe method.

Practice

1. What is the main purpose of an event subscriber in Laravel?

easy

A. To replace middleware in routing

B. To group multiple event handlers in one class for better organization

C. To directly dispatch events to the database

D. To handle HTTP requests and responses

Solution

1. Step 1: Understand event subscribers role

   Event subscribers group multiple event handlers in one class to keep code organized.

2. Step 2: Compare with other options

   Options A, B, and D describe unrelated Laravel features like middleware, database dispatch, and HTTP handling.

3. Final Answer:

   To group multiple event handlers in one class for better organization -> Option B

4. Quick Check:

   Event subscribers organize handlers = C [OK]

Hint: Subscribers group handlers in one class for neat code [OK]

Common Mistakes:

• Confusing subscribers with middleware
• Thinking subscribers dispatch events
• Mixing subscribers with HTTP controllers

2. Which method must a Laravel event subscriber class implement to register its event handlers?

easy

A. boot()

B. handle()

C. listen()

D. subscribe()

Solution

1. Step 1: Recall subscriber method

   Laravel event subscribers use the subscribe() method to register event handlers.

2. Step 2: Eliminate other methods

   handle() is for event listeners, listen() is used in EventServiceProvider, boot() is for service providers.

3. Final Answer:

   subscribe() -> Option D

4. Quick Check:

   subscribe() registers handlers = A [OK]

Hint: Subscribers use subscribe() to register handlers [OK]

Common Mistakes:

• Using handle() instead of subscribe()
• Confusing listen() with subscribe()
• Thinking boot() is for subscribers

3. Given this subscriber class, what will happen when the UserRegistered event is fired?

class UserEventSubscriber {
    public function subscribe($events) {
        $events->listen('UserRegistered', [self::class, 'onUserRegistered']);
    }

    public function onUserRegistered($event) {
        echo 'User registered: ' . $event->user->name;
    }
}

medium

A. Nothing happens because subscribe is not called automatically

B. It will throw a syntax error

C. It will echo the registered user's name

D. It will echo 'User registered:' without the name

Solution

1. Step 1: Understand event firing and subscriber listening

   The subscriber listens for 'UserRegistered' and calls onUserRegistered which echoes the user's name.

2. Step 2: Confirm subscribe method usage

   Laravel calls subscribe() automatically when registered, so the handler runs and echoes the message with the name.

3. Final Answer:

   It will echo the registered user's name -> Option C

4. Quick Check:

   Event triggers echo with name = A [OK]

Hint: subscribe() auto-registers handlers; echo shows user name [OK]

Common Mistakes:

• Thinking subscribe() must be called manually
• Assuming syntax error due to self::class
• Ignoring the event object passed to handler

4. Identify the error in this subscriber class:

class OrderSubscriber {
    public function subscribe($events) {
        $events->listen('OrderPlaced', 'handleOrderPlaced');
    }

    public function handleOrderPlaced($event) {
        // process order
    }
}

medium

A. The listener callback should be an array with class and method

B. The handleOrderPlaced method must be static

C. The subscribe method must return a value

D. The event name should be lowercase

Solution

1. Step 1: Check listener callback format

   Laravel expects the listener callback as an array with class and method when used in subscribers.

2. Step 2: Analyze given code

   The code uses a string 'handleOrderPlaced' instead of [self::class, 'handleOrderPlaced'], causing a runtime error.

3. Final Answer:

   The listener callback should be an array with class and method -> Option A

4. Quick Check:

   Listener callback must be array = D [OK]

Hint: Use [ClassName::class, 'method'] for subscriber callbacks [OK]

Common Mistakes:

• Passing method name as string only
• Thinking subscribe must return a value
• Assuming method must be static

5. You want to create a subscriber that listens to OrderPlaced and OrderShipped events. Which is the correct way to register both handlers in the subscribe method?

hard

A. public function subscribe($events) {
$events->listen('OrderPlaced', [self::class, 'handleOrderPlaced']);
$events->listen('OrderShipped', [self::class, 'handleOrderShipped']);
}

B. public function subscribe($events) {
$events->listen(['OrderPlaced', 'OrderShipped'], [self::class, 'handleOrder']);
}

C. public function subscribe($events) {
$events->listen('OrderPlaced', 'handleOrderPlaced');
$events->listen('OrderShipped', 'handleOrderShipped');
}

D. public function subscribe($events) {
$events->listen('OrderPlaced', self::handleOrderPlaced);
$events->listen('OrderShipped', self::handleOrderShipped);
}

Solution

1. Step 1: Understand correct listener registration

   Each event must be registered separately with an array callback [Class, method].

2. Step 2: Evaluate options

   public function subscribe($events) { $events->listen('OrderPlaced', [self::class, 'handleOrderPlaced']); $events->listen('OrderShipped', [self::class, 'handleOrderShipped']); } correctly registers both events with proper callbacks. public function subscribe($events) { $events->listen(['OrderPlaced', 'OrderShipped'], [self::class, 'handleOrder']); } wrongly groups events in one call. public function subscribe($events) { $events->listen('OrderPlaced', 'handleOrderPlaced'); $events->listen('OrderShipped', 'handleOrderShipped'); } uses strings instead of array callbacks. public function subscribe($events) { $events->listen('OrderPlaced', self::handleOrderPlaced); $events->listen('OrderShipped', self::handleOrderShipped); } uses invalid syntax without quotes.

3. Final Answer:

   public function subscribe($events) { $events->listen('OrderPlaced', [self::class, 'handleOrderPlaced']); $events->listen('OrderShipped', [self::class, 'handleOrderShipped']); } -> Option A

4. Quick Check:

   Separate listen calls with array callbacks = B [OK]

Hint: Register each event separately with [Class::class, 'method'] [OK]

Common Mistakes:

• Grouping multiple events in one listen call
• Using string method names without array
• Using invalid syntax without quotes