Bird
Raised Fist0
Laravelframework~10 mins

Defining events in Laravel - Interactive Code Practice

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to define a new event class in Laravel.

Laravel
php artisan make:event [1]
Drag options to blanks, or click blank then click option'
AEventListener
BUserRegistered
CController
DMiddleware
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'Controller' or 'Middleware' instead of an event name.
Confusing event creation with listener creation.
2fill in blank
medium

Complete the event class to implement the ShouldBroadcast interface.

Laravel
use Illuminate\Broadcasting\[1];

class UserRegistered implements [1]
{
    // Event properties and methods
}
Drag options to blanks, or click blank then click option'
AShouldBroadcast
BListener
CEvent
DBroadcastable
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'Listener' or 'Event' which are not interfaces for broadcasting.
Forgetting to import the interface.
3fill in blank
hard

Fix the error in the event constructor to assign the user property.

Laravel
public $user;

public function __construct([1] $user)
{
    $this->user = $user;
}
Drag options to blanks, or click blank then click option'
AUserController
BUserEvent
CUser
DUserModel
Attempts:
3 left
💡 Hint
Common Mistakes
Using controller or event class names instead of the model.
Missing the type hint entirely.
4fill in blank
hard

Fill in the blank to define the broadcastOn method returning a private channel.

Laravel
public function broadcastOn()
{
    return new [1]('user.' . $this->user->id);
}
Drag options to blanks, or click blank then click option'
APrivateChannel
BPublicChannel
CPresenceChannel
DBroadcastChannel
Attempts:
3 left
💡 Hint
Common Mistakes
Using public or presence channels when a private channel is needed.
5fill in blank
hard

Fill all three blanks to define the broadcastWith method returning event data.

Laravel
public function broadcastWith()
{
    return [
        '[1]' => $this->user->id,
        '[2]' => $this->user->name,
        '[3]' => $this->user->email,
    ];
}
Drag options to blanks, or click blank then click option'
Auser_id
Bname
Cemail
Did
Attempts:
3 left
💡 Hint
Common Mistakes
Using inconsistent or incorrect keys like 'user_id' instead of 'id'.
Missing keys or returning incomplete data.

Practice

(1/5)
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