Event dispatching in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when an event is dispatched with multiple listeners?

Consider a Laravel event dispatched with two listeners attached. What is the expected behavior when the event is fired?

Laravel

Event::dispatch(new UserRegistered($user));

// Two listeners are registered for UserRegistered event

A Both listeners run in the order they were registered, one after the other.

B Only the first listener runs; the second is ignored.

C Listeners run in parallel and may complete in any order.

D The event dispatch throws an error if multiple listeners exist.

💡 Hint

Think about how Laravel handles event listeners synchronously by default.

Laravel runs all listeners for an event synchronously in the order they were registered unless queued listeners are used.

📝 Syntax

intermediate

Which code correctly dispatches an event in Laravel?

Choose the correct syntax to dispatch a Laravel event named OrderShipped with an $order object.

A Event::fire(new OrderShipped($order));

B dispatch_event(OrderShipped($order));

C event(new OrderShipped($order));

D Event::dispatch(OrderShipped);

💡 Hint

Remember the helper function Laravel provides for dispatching events.

The event() helper function is the recommended way to dispatch events in Laravel.

🔧 Debug

advanced

Why does this event listener not run when the event is dispatched?

Given this listener class, why might it not be triggered when the event is dispatched?

Laravel

class SendWelcomeEmail implements ShouldQueue
{
    public function handle(UserRegistered $event)
    {
        Mail::to($event->user->email)->send(new WelcomeEmail());
    }
}

// Event dispatched as: event(new UserRegistered($user));

A The event is dispatched incorrectly; it should use Event::dispatch().

B The event class name is misspelled in the listener handle method.

C The listener class does not implement the Listener interface.

D The listener is queued but the queue worker is not running.

💡 Hint

Think about what happens when a listener implements ShouldQueue.

Listeners implementing ShouldQueue are pushed to a queue. If no queue worker is running, the listener won't execute.

❓ state_output

advanced

What is the value of $count after dispatching the event?

Consider this code snippet:

class CounterListener
{
    public static int $count = 0;

    public function handle(SomeEvent $event)
    {
        self::$count++;
    }
}

Event::listen(SomeEvent::class, [CounterListener::class, 'handle']);

Event::dispatch(new SomeEvent());
Event::dispatch(new SomeEvent());

$count = CounterListener::$count;

What is the value of $count after running this code?

A 2

B 1

C 0

D Throws an error because static property access is invalid.

💡 Hint

Each event dispatch triggers the listener once.

The listener increments the static counter each time the event is dispatched, so after two dispatches, the count is 2.

🧠 Conceptual

expert

What error occurs if an event class constructor requires a parameter but none is passed during dispatch?

Given an event class PaymentProcessed with a constructor requiring a $paymentId parameter, what happens if you dispatch it without arguments like event(new PaymentProcessed());?

Laravel

class PaymentProcessed
{
    public function __construct(public int $paymentId) {}
}

A The event dispatch silently succeeds with a null paymentId.

B A TypeError is thrown indicating a missing argument for the constructor.

C A runtime exception occurs because the event class is abstract.

D The event dispatch triggers but the listener receives an empty event object.

💡 Hint

Think about PHP constructor requirements when instantiating objects.

PHP throws a TypeError if a required constructor argument is missing when creating a new object.

Practice

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

easy

A. To create new routes for the application

B. To directly update the database records

C. To send messages about actions happening in the application

D. To handle user authentication automatically

Solution

1. Step 1: Understand event dispatching concept

   Event dispatching is used to send messages or signals when something happens in the app.

2. Step 2: Identify the correct purpose

   It is not about database updates, routing, or authentication but about notifying parts of the app.

3. Final Answer:

   To send messages about actions happening in the application -> Option C

4. Quick Check:

   Event dispatching = sending messages [OK]

Hint: Events notify parts of app about actions [OK]

Common Mistakes:

• Confusing events with database operations
• Thinking events create routes
• Assuming events handle authentication

2. Which of the following is the correct syntax to dispatch an event named UserRegistered with a user object $user?

easy

A. sendEvent('UserRegistered', $user);

B. dispatch(UserRegistered, $user);

C. UserRegistered::dispatch($user);

D. event(new UserRegistered($user));

Solution

1. Step 1: Recall Laravel event dispatch syntax

   Laravel uses the global event() helper with a new event instance.

2. Step 2: Match syntax with options

   Only event(new UserRegistered($user)); matches Laravel's pattern.

3. Final Answer:

   event(new UserRegistered($user)); -> Option D

4. Quick Check:

   Use event(new EventName($data)) [OK]

Hint: Use event(new EventName($data)) to dispatch [OK]

Common Mistakes:

• Using dispatch() without new keyword
• Calling event as a static method
• Using non-existent sendEvent function

3. Given the following code, what will be the output?

class OrderPlaced {
  public $orderId;
  public function __construct($orderId) {
    $this->orderId = $orderId;
  }
}

// Dispatch event
event(new OrderPlaced(123));

// Listener logs the order ID
Log::info('Order placed with ID: ' . 123);

medium

A. Logs: 'Order placed with ID: 123'

B. Logs: 'Order placed with ID: OrderPlaced'

C. No log output because event is not handled

D. Syntax error due to missing listener

Solution

1. Step 1: Understand event dispatch and listener

   The event OrderPlaced is dispatched with order ID 123, and the listener logs this ID.

2. Step 2: Check the log output

   The log line explicitly outputs 'Order placed with ID: 123'.

3. Final Answer:

   Logs: 'Order placed with ID: 123' -> Option A

4. Quick Check:

   Listener logs correct order ID [OK]

Hint: Listener logs event data as given [OK]

Common Mistakes:

• Assuming event dispatch alone logs output
• Confusing event class name with data
• Expecting error without listener registration

4. Identify the error in this event dispatching code:

event(UserRegistered($user));

medium

A. Missing the 'new' keyword before the event class

B. Incorrect event name, should be 'UserRegister'

C. Event dispatching requires a string, not an object

D. The variable $user is not passed correctly

Solution

1. Step 1: Check event dispatch syntax

   Laravel requires creating a new instance of the event class using new.

2. Step 2: Identify missing 'new' keyword

   The code calls UserRegistered($user) like a function, missing new.

3. Final Answer:

   Missing the 'new' keyword before the event class -> Option A

4. Quick Check:

   Use new EventClass($data) when dispatching [OK]

Hint: Always use new keyword before event class [OK]

Common Mistakes:

• Calling event class as function without new
• Wrong event class name
• Passing wrong data type

5. You want to dispatch an event ProfileUpdated only if the user's email has changed. Which code correctly implements this conditional event dispatch?

hard

A. ProfileUpdated::dispatch($user) when $user->email != old_email;

B. if ($user->isDirty('email')) { event(new ProfileUpdated($user)); }

C. event(new ProfileUpdated($user)) if $user->email_changed();

D. if ($user->email !== null) { dispatch(ProfileUpdated($user)); }

Solution

1. Step 1: Understand Laravel's model change detection

   The isDirty('email') method checks if the email attribute changed.

2. Step 2: Verify correct conditional event dispatch

   if ($user->isDirty('email')) { event(new ProfileUpdated($user)); } uses correct syntax and condition to dispatch event only if email changed.

3. Final Answer:

   if ($user->isDirty('email')) { event(new ProfileUpdated($user)); } -> Option B

4. Quick Check:

   Use isDirty() to check changes before event [OK]

Hint: Use isDirty('field') to check changes before event [OK]

Common Mistakes:

• Using incorrect syntax for condition
• Calling dispatch without new keyword
• Checking wrong condition for email change