Defining events in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output when this Laravel event is fired?

Consider this Laravel event class and listener setup. What will be the output when the event is fired?

Laravel

namespace App\Events;

use Illuminate\Foundation\Events\Dispatchable;
use Illuminate\Queue\SerializesModels;

class UserRegistered
{
    use Dispatchable, SerializesModels;

    public $username;

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

// Listener
namespace App\Listeners;

class SendWelcomeEmail
{
    public function handle($event)
    {
        echo "Welcome email sent to {$event->username}";
    }
}

// Somewhere in controller or service
use App\Events\UserRegistered;

event(new UserRegistered('Alice'));

A Welcome email sent to Alice

B Error: Undefined property username

C No output because listener is not registered

D Welcome email sent to

💡 Hint

Think about whether the listener is automatically called just by firing the event.

In Laravel, firing an event does not automatically call listeners unless they are registered in the EventServiceProvider or manually attached. Since the listener is not registered here, no output occurs.

📝 Syntax

intermediate

Which option correctly defines a Laravel event class with a public property?

Choose the correct Laravel event class definition that includes a public property $data and uses the recommended traits.

A

class DataUpdated {
    use Dispatchable, SerializesModels;
    public $data;
    public function __construct($data) {
        $this->data = $data;
    }
}

B

class DataUpdated {
    use Dispatchable, SerializesModels
    public $data;
    function __construct($data) {
        $this->data = $data;
    }
}

C

class DataUpdated {
    public $data;
    public function __construct($data) {
        $this->data = $data;
    }
}

D

class DataUpdated {
    use Dispatchable, SerializesModels;
    private $data;
    public function __construct($data) {
        $this->data = $data;
    }
}

💡 Hint

Remember to include semicolons after traits and use public visibility for properties to be accessible.

Option A correctly uses the traits with semicolons, declares the property as public, and defines the constructor properly. Option A misses traits, B misses semicolon after traits, and D uses private property which is not accessible outside.

❓ state_output

advanced

What is the value of $event->count after firing this event multiple times?

Given this Laravel event class, what will be the value of $event->count after firing the event three times with counts 1, 2, and 3?

Laravel

namespace App\Events;

use Illuminate\Foundation\Events\Dispatchable;
use Illuminate\Queue\SerializesModels;

class CounterUpdated
{
    use Dispatchable, SerializesModels;

    public $count;

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

// Firing events
$event1 = new CounterUpdated(1);
event($event1);
$event2 = new CounterUpdated(2);
event($event2);
$event3 = new CounterUpdated(3);
event($event3);

// What is $event3->count?

A 1

B null

C 2

D 3

💡 Hint

Each event instance holds its own data passed in constructor.

Each event instance is separate. The last event created has count 3, so $event3->count is 3.

🔧 Debug

advanced

Why does this Laravel event listener not receive the event data?

Examine the event and listener code below. Why does the listener not print the username when the event is fired?

Laravel

// Event
namespace App\Events;

use Illuminate\Foundation\Events\Dispatchable;
use Illuminate\Queue\SerializesModels;

class UserLoggedIn
{
    use Dispatchable, SerializesModels;

    public $username;

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

// Listener
namespace App\Listeners;

class LogLogin
{
    public function handle()
    {
        echo "User logged in: " . $this->username;
    }
}

// Firing event
event(new \App\Events\UserLoggedIn('Bob'));

A Listener handle method lacks the event parameter to receive event data

B Event class is missing the SerializesModels trait

C Event is not fired correctly with event() helper

D Listener class is missing a constructor

💡 Hint

Check the listener's handle method signature.

The listener's handle method must accept the event object as a parameter to access its properties. Without it, $this->username is undefined.

🧠 Conceptual

expert

Which statement best describes Laravel event broadcasting?

Choose the statement that correctly explains Laravel event broadcasting.

A Broadcasting queues events to run only after database transactions commit

B Broadcasting sends events to client-side JavaScript in real-time using channels and websockets

C Broadcasting automatically logs all events to Laravel log files

D Broadcasting delays event listeners to run asynchronously on the server

💡 Hint

Think about how Laravel sends events beyond the server to the browser.

Laravel event broadcasting allows server events to be sent to client-side JavaScript in real-time using channels and websockets, enabling live updates.

Practice

1. What is the main purpose of defining events in a Laravel application?

easy

A. To respond to actions in a clean and organized way

B. To directly modify database tables

C. To create user interface components

D. To handle HTTP routing

Solution

1. Step 1: Understand the role of events

   Events in Laravel are designed to help the app respond to actions or changes without mixing code logic.

2. Step 2: Compare with other options

   Modifying database tables, creating UI components, and handling routing are done by other parts of Laravel, not events.

3. Final Answer:

   To respond to actions in a clean and organized way -> Option A

4. Quick Check:

   Events = Respond to actions [OK]

Hint: Events handle actions, not UI or database directly [OK]

Common Mistakes:

• Confusing events with database migrations
• Thinking events create UI elements
• Mixing events with routing logic

2. Which artisan command correctly creates a new event named UserRegistered?

easy

A. php artisan make:event UserRegistered

B. php artisan event:create UserRegistered

C. php artisan make:event --new UserRegistered

D. php artisan create:event UserRegistered

Solution

1. Step 1: Recall the artisan command for events

   The correct command to create an event is php artisan make:event EventName.

2. Step 2: Check each option

   Only php artisan make:event UserRegistered matches the correct syntax. Others use invalid commands or flags.

3. Final Answer:

   php artisan make:event UserRegistered -> Option A

4. Quick Check:

   make:event = create event [OK]

Hint: Use 'make:event' with artisan to create events [OK]

Common Mistakes:

• Using 'event:create' instead of 'make:event'
• Adding unnecessary flags like '--new'
• Swapping command order

3. Given this event class snippet:

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

What will be the correct way to fire this event with an $order object?

medium

A. event(OrderShipped($order));

B. OrderShipped::fire($order);

C. event(new OrderShipped($order));

D. fire_event('OrderShipped', $order);

Solution

1. Step 1: Understand how to fire events in Laravel

   Events are fired by calling the global event() helper with a new instance of the event class.

2. Step 2: Check each option

   event(new OrderShipped($order)); correctly uses event(new OrderShipped($order)). event(OrderShipped($order)); misses new, C and D use invalid syntax.

3. Final Answer:

   event(new OrderShipped($order)); -> Option C

4. Quick Check:

   Fire event = event(new EventClass) [OK]

Hint: Always use 'new' keyword inside event() to fire events [OK]

Common Mistakes:

• Omitting 'new' keyword when firing event
• Trying to call static fire methods
• Using non-existent helper functions

4. Identify the error in this event class definition:

class ProductCreated {
    public $product;
    public function ProductCreated($product) {
        $this->product = $product;
    }
}

medium

A. Property should be private, not public

B. Missing public keyword before property

C. Event class must extend a base Event class

D. Constructor method name should be __construct, not class name

Solution

1. Step 1: Check constructor syntax in PHP

   In modern PHP (and Laravel), constructors must be named __construct, not the class name.

2. Step 2: Verify other options

   Property visibility is correct as public, extending base class is optional, so only constructor name is wrong.

3. Final Answer:

   Constructor method name should be __construct, not class name -> Option D

4. Quick Check:

   Constructor = __construct method [OK]

Hint: Use __construct() for constructors, not class name [OK]

Common Mistakes:

• Using old PHP constructor style
• Forgetting visibility keywords
• Assuming event classes must extend a base class

5. You want to define an event InvoicePaid that carries an Invoice object and a payment amount. Which is the best way to define its constructor?

hard

A. public function __construct(array $data) { $this->invoice = $data['invoice']; $this->amount = $data['amount']; }

B. public function __construct(Invoice $invoice, float $amount) { $this->invoice = $invoice; $this->amount = $amount; }

C. public function InvoicePaid(Invoice $invoice, float $amount) { $this->invoice = $invoice; $this->amount = $amount; }

D. public function __construct($invoice, $amount) { $invoice = $invoice; $amount = $amount; }

Solution

1. Step 1: Check constructor naming and parameter types

   The constructor must be named __construct and accept typed parameters for clarity and safety.

2. Step 2: Verify property assignments

   public function __construct(Invoice $invoice, float $amount) { $this->invoice = $invoice; $this->amount = $amount; } correctly assigns parameters to properties. public function __construct($invoice, $amount) { $invoice = $invoice; $amount = $amount; } assigns parameters to themselves (wrong). public function InvoicePaid(Invoice $invoice, float $amount) { $this->invoice = $invoice; $this->amount = $amount; } uses old constructor name. public function __construct(array $data) { $this->invoice = $data['invoice']; $this->amount = $data['amount']; } uses array but less clear and no type safety.

3. Final Answer:

   public function __construct(Invoice $invoice, float $amount) { $this->invoice = $invoice; $this->amount = $amount; } -> Option B

4. Quick Check:

   Use __construct with typed params and assign to properties [OK]

Hint: Use __construct with typed params and assign to $this->props [OK]

Common Mistakes:

• Using old constructor method name
• Assigning parameters to themselves
• Using untyped or array parameters without clarity