Model events and observers in Laravel - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to register an observer for the User model.

Laravel

User::[1](UserObserver::class);

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

Awatch

Blisten

Chandle

Dobserve

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'listen' instead of 'observe' causes errors because 'listen' is for events, not observers.

Using 'watch' or 'handle' are not valid methods on the model.

In Laravel, you register an observer on a model using the observe method.

2fill in blank

medium

Complete the observer method name to handle the event when a model is saved.

Laravel

public function [1](User $user) {
    // code here
}

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

Asaved

Bdeleting

Cupdated

Dcreating

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'creating' triggers before save, not after.

Using 'updated' triggers only on update, not on create.

The saved method in an observer is called after a model is saved (created or updated).

3fill in blank

hard

Fix the error in the observer method name to correctly handle model deletion.

Laravel

public function [1](User $user) {
    // code here
}

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

Adelete

Bdeleted

Cdeleting

Ddestroy

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'delete' causes method not found errors.

Using 'deleted' triggers after deletion, not before.

The deleting method is called before a model is deleted. Using delete or destroy is incorrect.

4fill in blank

hard

Fill both blanks to create a model observer method that runs after a model is updated.

Laravel

public function [1](User $user) {
    // This runs [2] the model update
}

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

Aupdated

Bbefore

Cafter

Dupdating

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'updating' runs before update, not after.

Writing 'before' in the comment is incorrect for this method.

The updated method runs after the model update is complete.

5fill in blank

hard

Fill all three blanks to define an observer method that runs before a model is created and logs the model's name.

Laravel

public function [1](User $user) {
    Log::info('Creating user: ' . $user->[2]);
    // Additional code [3]
}

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

Acreating

Bname

C// here

Dcreated

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'created' runs after creation, not before.

Accessing a wrong property instead of 'name'.

The creating method runs before the model is created. Accessing $user->name gets the user's name. The comment placeholder is just a marker.

Practice

1. What is the main purpose of model events in Laravel?

easy

A. To react automatically when a model is created, updated, or deleted

B. To define database table relationships

C. To create database migrations

D. To write raw SQL queries

Solution

1. Step 1: Understand model events

   Model events are hooks that trigger when a model changes, like creation or deletion.

2. Step 2: Identify their purpose

   They let you run code automatically on these changes, such as logging or notifications.

3. Final Answer:

   To react automatically when a model is created, updated, or deleted -> Option A

4. Quick Check:

   Model events = react on model changes [OK]

Hint: Model events trigger on data changes automatically [OK]

Common Mistakes:

• Confusing events with database migrations
• Thinking events define relationships
• Assuming events run SQL queries directly

2. Which of the following is the correct way to register an observer for a model in Laravel?

easy

A. User::addObserver('UserObserver');

B. User::observe(UserObserver::class);

C. User::registerObserver(UserObserver);

D. User::attachObserver(UserObserver::class);

Solution

1. Step 1: Recall observer registration syntax

   Laravel uses the static method observe() on the model to register observers.

2. Step 2: Match correct syntax

   The correct syntax is Model::observe(ObserverClass::class); which matches User::observe(UserObserver::class);.

3. Final Answer:

   User::observe(UserObserver::class); -> Option B

4. Quick Check:

   Register observer = observe() method [OK]

Hint: Use observe() method with ::class for observers [OK]

Common Mistakes:

• Using wrong method names like registerObserver
• Passing observer as string instead of ::class
• Confusing attachObserver with observe

3. Given this observer method in Laravel:

public function created(User $user) {
    Log::info('User created: ' . $user->id);
}

What happens when a new User model is saved?

medium

A. An error is thrown because created() is invalid

B. The user is deleted immediately

C. Nothing happens automatically

D. A log entry with the new user's ID is created

Solution

1. Step 1: Understand the created() observer method

   The created() method runs after a model is saved for the first time.

2. Step 2: Analyze the method body

   It logs info with the new user's ID, so a log entry is made.

3. Final Answer:

   A log entry with the new user's ID is created -> Option D

4. Quick Check:

   created() logs user ID after save [OK]

Hint: created() runs after first save, logs info [OK]

Common Mistakes:

• Thinking created() deletes the model
• Assuming created() does nothing
• Confusing created() with invalid method

4. What is wrong with this observer registration code?

public function boot() {
    User::observe();
}

medium

A. The observe() method is called without passing the observer class

B. The boot() method should be named bootObserver()

C. User model cannot have observers

D. The observe() method should be called on the observer class

Solution

1. Step 1: Check observe() method usage

   observe() requires the observer class as an argument to register it.

2. Step 2: Identify missing argument

   Here, observe() is called with no arguments, so it will cause an error.

3. Final Answer:

   The observe() method is called without passing the observer class -> Option A

4. Quick Check:

   observe() needs observer class argument [OK]

Hint: Always pass observer class to observe() [OK]

Common Mistakes:

• Calling observe() without arguments
• Renaming boot() incorrectly
• Calling observe() on wrong class

5. You want to log a message every time a Post model is updated, but only if the title has changed. How should you implement this in a PostObserver?

hard

A. Use the deleted(Post $post) method and check if $post->isDirty('title') is true

B. Use the saving(Post $post) method and check if $post->wasChanged('title') is true

C. Use the updated(Post $post) method and check if $post->wasChanged('title') is true

D. Use the created(Post $post) method and check if $post->title is not empty

Solution

1. Step 1: Identify correct event for update

   The updated() method runs after a model is updated, suitable for this task.

2. Step 2: Check how to detect changed attributes

   wasChanged('title') returns true if the title attribute was changed during the update.

3. Step 3: Combine logic

   Inside updated(), check wasChanged('title') to log only when title changed.

4. Final Answer:

   Use the updated(Post $post) method and check if $post->wasChanged('title') is true -> Option C

5. Quick Check:

   updated() + wasChanged('title') detects title changes [OK]

Hint: Use updated() and wasChanged() to detect attribute changes [OK]

Common Mistakes:

• Using created() or deleted() for updates
• Using wasChanged() inside saving() which runs before update
• Checking isDirty() in deleted() event