When working with Eloquent models, it is common to take advantage of events dispatched through the model lifecycle. There are a few different ways to do this, and in this tutorial I'll cover them and explain the pros and cons of each. [Related recommendations: laravel video tutorial]
I will use the same example for each method so that you can compare directly. This example assigns the model's UUID property to the UUID during creation of the model itself.
Our first approach uses the model's static bootstrap method to register the behavior. This allows us to work directly on the model and create it when the model is created .
declare(strict_types=1); namespace App\Models; use Illuminate\Database\Eloquent\Model; use Illuminate\Support\Str; class Office extends Model { public static function boot(): void { static::creating(fn (Model $model) => $model->uuid = Str::uuid(), ); } }
This approach is great for small, direct reactions to model events, like adding UUIDs, because it's very easy to understand and you can see exactly what's happening on the model. The biggest problem with this approach is code duplication, if you have multiple models that need to be assigned UUIDs, you will be doing the same thing repeatedly.
This leads us nicely into the second approach, using a feature. In Laravel, if you create a method on a trait that starts with boot
and ends with the trait name, your models can inherit the trait and automatically start them. Here is an example:
declare(strict_types=1); namespace App\Models\Concerns; use Illuminate\Database\Eloquent\Model; use Illuminate\Support\Str; trait HasUuid { public static function bootHasUuid(): void { static::creating(fn (Model $model) => $model->uuid = Str::uuid(), ); } }
Using traits allows you to add this behavior to every model that requires it and is easy to implement. My biggest drawback is that stacking these behaviors can cause problems when multiple features want to take advantage of the same model event. They start fighting for priority and it quickly becomes a mess.
This leads us to the next option, model observers. A model observer is a class-based way to respond to model events, where the method corresponds to the specific event that was triggered.
declare(strict_types=1); namespace App\Observers; use Illuminate\Database\Eloquent\Model; use Illuminate\Support\Str; class OfficeObserver { public function creating(Model $model): void { $model->uuid = Str::uuid(); } }
This class needs to be registered somewhere, either with the service provider or the model itself (which is where I recommend it). Registering this observer in the model allows you to see the side effects of changing eloquent behavior at the model level. The problem with hiding it from the service provider is that it's hard to know unless everyone knows it exists. The biggest disadvantage of this approach is its visibility. In my opinion this method is great when used correctly.
Another way to solve this problem is to take advantage of the $dispatchesEvents
property of the Eloquent model itself. This is a property on every Eloquent model that allows you to list events to listen to and the classes to call for those events.
declare(strict_types=1); namespace App\Models; use Illuminate\Database\Eloquent\Model; use Illuminate\Support\Str; class Office extends Model { protected $dispatchesEvents = [ 'creating' => SetModelUuid::class, ]; }
SetModelUuid
will be instantiated during the life cycle of the Eloquent model, which is your opportunity to add behaviors and properties to the model.
declare(strict_types=1); namespace App\Models\Events; use Illuminate\Database\Eloquent\Model; use Illuminate\Support\Str; class SetModelUuid { public function __construct(Model $model) { $model->uuid = Str::uuid(); } }
This approach is one of the cleanest and easiest to understand because the model has a lot of visibility and you can easily share this class between models. The biggest question you'll face is whether you need to trigger multiple actions on model events.
Anyway, honestly, there is no right way to do this. You can choose any of the above methods and they will all work, but you should choose the method that works for you and your specific use case. I'd like to see more options for this specific feature.
For example, if you need to add multiple properties to a model on model events, observers are a good choice. However, is this the best option? What if we use the dispatch events attribute to run a custom pipeline for this model?
declare(strict_types=1); namespace App\Models\Pipelines; use App\Models\Office class OfficeCreatingPipeline { public function __construct(Office $model) { app(Pipeline::class) ->send($model) ->through([ ApplyUuidProperty::class, TapCreatedBy::class, ]); } }
As you can see, we can start using pipelines to add multiple behaviors for event modeling. Now, this hasn't been tested, so I don't know 100% if it's possible - but as a concept, it could open up a composable way to react to model events.
How do you handle model events in your Laravel project? Tell us on Twitter!
Original address: https://laravel-news.com/working-with-laravel-model-events
Translation address: https://learnku.com/laravel/ t/71183
For more programming related knowledge, please visit: Programming Video! !
The above is the detailed content of Let's talk about how to use model events in Laravel. For more information, please follow other related articles on the PHP Chinese website!

Laravel's core functions in back-end development include routing system, EloquentORM, migration function, cache system and queue system. 1. The routing system simplifies URL mapping and improves code organization and maintenance. 2.EloquentORM provides object-oriented data operations to improve development efficiency. 3. The migration function manages the database structure through version control to ensure consistency. 4. The cache system reduces database queries and improves response speed. 5. The queue system effectively processes large-scale data, avoid blocking user requests, and improve overall performance.

Laravel performs strongly in back-end development, simplifying database operations through EloquentORM, controllers and service classes handle business logic, and providing queues, events and other functions. 1) EloquentORM maps database tables through the model to simplify query. 2) Business logic is processed in controllers and service classes to improve modularity and maintainability. 3) Other functions such as queue systems help to handle complex needs.

The Laravel development project was chosen because of its flexibility and power to suit the needs of different sizes and complexities. Laravel provides routing system, EloquentORM, Artisan command line and other functions, supporting the development of from simple blogs to complex enterprise-level systems.

The comparison between Laravel and Python in the development environment and ecosystem is as follows: 1. The development environment of Laravel is simple, only PHP and Composer are required. It provides a rich range of extension packages such as LaravelForge, but the extension package maintenance may not be timely. 2. The development environment of Python is also simple, only Python and pip are required. The ecosystem is huge and covers multiple fields, but version and dependency management may be complex.

How does Laravel play a role in backend logic? It simplifies and enhances backend development through routing systems, EloquentORM, authentication and authorization, event and listeners, and performance optimization. 1. The routing system allows the definition of URL structure and request processing logic. 2.EloquentORM simplifies database interaction. 3. The authentication and authorization system is convenient for user management. 4. The event and listener implement loosely coupled code structure. 5. Performance optimization improves application efficiency through caching and queueing.

Laravel's popularity includes its simplified development process, providing a pleasant development environment, and rich features. 1) It absorbs the design philosophy of RubyonRails, combining the flexibility of PHP. 2) Provide tools such as EloquentORM, Blade template engine, etc. to improve development efficiency. 3) Its MVC architecture and dependency injection mechanism make the code more modular and testable. 4) Provides powerful debugging tools and performance optimization methods such as caching systems and best practices.

Both Django and Laravel are full-stack frameworks. Django is suitable for Python developers and complex business logic, while Laravel is suitable for PHP developers and elegant syntax. 1.Django is based on Python and follows the "battery-complete" philosophy, suitable for rapid development and high concurrency. 2.Laravel is based on PHP, emphasizing the developer experience, and is suitable for small to medium-sized projects.

PHP and Laravel are not directly comparable, because Laravel is a PHP-based framework. 1.PHP is suitable for small projects or rapid prototyping because it is simple and direct. 2. Laravel is suitable for large projects or efficient development because it provides rich functions and tools, but has a steep learning curve and may not be as good as pure PHP.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

SublimeText3 Linux new version
SublimeText3 Linux latest version

SAP NetWeaver Server Adapter for Eclipse
Integrate Eclipse with SAP NetWeaver application server.

VSCode Windows 64-bit Download
A free and powerful IDE editor launched by Microsoft

Dreamweaver Mac version
Visual web development tools

Atom editor mac version download
The most popular open source editor