Model events let you run code automatically when something happens to your data. Observers help organize this code neatly.
Model events and observers in Laravel
php // Creating an observer class class UserObserver { public function created(User $user) { // code to run after a user is created } public function updated(User $user) { // code to run after a user is updated } } // Registering the observer in a service provider User::observe(UserObserver::class);
Observer methods match model events like created, updated, deleted.
Register observers usually in AppServiceProvider or a dedicated provider.
php class PostObserver { public function deleting(Post $post) { // Remove related comments before deleting a post $post->comments()->delete(); } } Post::observe(PostObserver::class);
php class OrderObserver { public function created(Order $order) { // Send notification when order is created Notification::send($order->user, new OrderPlaced($order)); } } Order::observe(OrderObserver::class);
This example shows a User model and a UserObserver that logs a message when a user is created. The observer is registered in the AppServiceProvider.
<?php namespace App\Models; use Illuminate\Database\Eloquent\Model; class User extends Model { // User model code } namespace App\Observers; use App\Models\User; use Illuminate\Support\Facades\Log; class UserObserver { public function created(User $user) { Log::info("User created: {$user->email}"); } } namespace App\Providers; use Illuminate\Support\ServiceProvider; use App\Models\User; use App\Observers\UserObserver; class AppServiceProvider extends ServiceProvider { public function boot() { User::observe(UserObserver::class); } } // When a new user is created, a log entry is made automatically.
Model events include: creating, created, updating, updated, deleting, deleted, saving, saved, restoring, restored.
Observers keep your code clean by separating event logic from models.
Remember to register observers to activate them.
Model events let you run code when data changes.
Observers organize event code in separate classes.
Register observers to connect them with models.
Practice
Solution
Step 1: Understand model events
Model events are hooks that trigger when a model changes, like creation or deletion.Step 2: Identify their purpose
They let you run code automatically on these changes, such as logging or notifications.Final Answer:
To react automatically when a model is created, updated, or deleted -> Option AQuick Check:
Model events = react on model changes [OK]
- Confusing events with database migrations
- Thinking events define relationships
- Assuming events run SQL queries directly
Solution
Step 1: Recall observer registration syntax
Laravel uses the static method observe() on the model to register observers.Step 2: Match correct syntax
The correct syntax is Model::observe(ObserverClass::class); which matches User::observe(UserObserver::class);.Final Answer:
User::observe(UserObserver::class); -> Option BQuick Check:
Register observer = observe() method [OK]
- Using wrong method names like registerObserver
- Passing observer as string instead of ::class
- Confusing attachObserver with observe
public function created(User $user) {
Log::info('User created: ' . $user->id);
}What happens when a new User model is saved?
Solution
Step 1: Understand the created() observer method
The created() method runs after a model is saved for the first time.Step 2: Analyze the method body
It logs info with the new user's ID, so a log entry is made.Final Answer:
A log entry with the new user's ID is created -> Option DQuick Check:
created() logs user ID after save [OK]
- Thinking created() deletes the model
- Assuming created() does nothing
- Confusing created() with invalid method
public function boot() {
User::observe();
}Solution
Step 1: Check observe() method usage
observe() requires the observer class as an argument to register it.Step 2: Identify missing argument
Here, observe() is called with no arguments, so it will cause an error.Final Answer:
The observe() method is called without passing the observer class -> Option AQuick Check:
observe() needs observer class argument [OK]
- Calling observe() without arguments
- Renaming boot() incorrectly
- Calling observe() on wrong class
Solution
Step 1: Identify correct event for update
The updated() method runs after a model is updated, suitable for this task.Step 2: Check how to detect changed attributes
wasChanged('title') returns true if the title attribute was changed during the update.Step 3: Combine logic
Inside updated(), check wasChanged('title') to log only when title changed.Final Answer:
Use the updated(Post $post) method and check if $post->wasChanged('title') is true -> Option CQuick Check:
updated() + wasChanged('title') detects title changes [OK]
- Using created() or deleted() for updates
- Using wasChanged() inside saving() which runs before update
- Checking isDirty() in deleted() event
Ready to prove it?
Pass the test and this pattern moves unknown
