Event dispatching in Laravel - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to dispatch an event named UserRegistered.

Laravel

event(new [1]());

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

AUserUpdated

BUserCreated

CUserRegistered

DUserLogin

Attempts:

3 left

💡 Hint

Common Mistakes

Using an event class name that does not exist.

Forgetting to use the new keyword before the event class.

The event() helper dispatches the event instance. Here, UserRegistered is the correct event class to dispatch.

2fill in blank

medium

Complete the code to listen for the UserRegistered event in the EventServiceProvider.

Laravel

'UserRegistered' => [[1]::class],

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

ALogUserLogin

BSendWelcomeEmail

CUpdateUserStats

DNotifyAdmin

Attempts:

3 left

💡 Hint

Common Mistakes

Using a listener that does not relate to the event.

Forgetting to add ::class after the listener name.

Listeners handle events. SendWelcomeEmail is a typical listener for UserRegistered event.

3fill in blank

hard

Fix the error in dispatching the event using the Event facade.

Laravel

Event::[1](new UserRegistered($user));

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

Adispatch

Bsend

Cfire

Dtrigger

Attempts:

3 left

💡 Hint

Common Mistakes

Using deprecated or incorrect method names like fire.

Confusing event dispatching with other actions.

The correct method to dispatch an event using the Event facade is dispatch.

4fill in blank

hard

Fill both blanks to create an event listener class that handles UserRegistered event.

Laravel

public function handle([1] $event)
{
    [2];
}

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

AUserRegistered

B$event->user->sendWelcomeEmail()

C$event->sendNotification()

DUserLogin

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong event class in the handle method parameter.

Calling a method that does not exist on the event object.

The handle method receives the event instance, here UserRegistered. Inside, it calls a method on the user to send a welcome email.

5fill in blank

hard

Fill all three blanks to dispatch a queued event with delay.

Laravel

UserRegistered::[1]()->delay(now()->addMinutes([2]))->[3]();

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

Adispatch

B10

CdispatchSync

DdispatchAfterResponse

Attempts:

3 left

💡 Hint

Common Mistakes

Using synchronous dispatch when queuing is intended.

Forgetting to specify delay time as a number.

Confusing dispatch methods.

Use dispatch to queue the event, set delay with delay(), and dispatchAfterResponse to dispatch after HTTP response.

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