創(chuàng)建事件和監(jiān)聽(tīng)器：使用Artisan命令生成UserRegistered事件及SendWelcomeEmail、LogUserRegistration監(jiān)聽(tīng)器；2. 定義事件類：在UserRegistered構(gòu)造函數(shù)中註入用戶實(shí)例以便監(jiān)聽(tīng)器訪問(wèn)；3. 編寫監(jiān)聽(tīng)器邏輯：SendWelcomeEmail發(fā)送歡迎郵件，LogUserRegistration記錄用戶註冊(cè)日誌；4. 註冊(cè)事件與監(jiān)聽(tīng)器：在EventServiceProvider的$listen數(shù)組中綁定事件與監(jiān)聽(tīng)器；5. 分發(fā)事件：在用戶註冊(cè)後通過(guò)event()或Event::dispatch()觸發(fā)UserRegistered事件，使監(jiān)聽(tīng)器自動(dòng)執(zhí)行；6. 可選啟用事件自動(dòng)發(fā)現(xiàn)：設(shè)置shouldDiscoverEvents返回true並運(yùn)行event:cache命令以自動(dòng)註冊(cè)監(jiān)聽(tīng)器；7. 最佳實(shí)踐：保持監(jiān)聽(tīng)器單一職責(zé)，耗時(shí)任務(wù)使用ShouldQueue接口實(shí)現(xiàn)隊(duì)列處理，避免在事件中編寫複雜邏輯。該模式通過(guò)解耦業(yè)務(wù)邏輯提升應(yīng)用可維護(hù)性和擴(kuò)展性，適用於通知、日誌、分析等場(chǎng)景。

Laravel Events and Listeners are a powerful way to make your application more modular and maintainable by decoupling actions from the code that triggers them. Instead of writing long, tightly coupled logic in your controllers or models, you can dispatch events and let listeners react to them. This tutorial walks you through setting up and using events and listeners in Laravel with a practical example.

What Are Events and Listeners?

• Event : Something that happened in your app (eg, a user registered).
• Listener : A class that reacts to that event (eg, send a welcome email, log activity).

This pattern follows the observer pattern , allowing one part of your app to notify others without knowing who's listening.

Step 1: Generate an Event and Listener

Laravel makes it easy to create events and listeners using Artisan commands.

Let's say we want to send a welcome email and log user registration.

Create the Event

 php artisan make:event UserRegistered

This creates a file: app/Events/UserRegistered.php

Create the Listener

 php artisan make:listener SendWelcomeEmail --event=UserRegistered
php artisan make:listener LogUserRegistration --event=UserRegistered

This creates:

• app/Listeners/SendWelcomeEmail.php
• app/Listeners/LogUserRegistration.php

You can also create listeners without specifying the event and wire them manually later.

Step 2: Define the Event Class

Open app/Events/UserRegistered.php . It should look like this:

 <?php

namespace App\Events;

use App\Models\User;
use Illuminate\Broadcasting\Channel;
use Illuminate\Broadcasting\InteractsWithSockets;
use Illuminate\Broadcasting\PresenceChannel;
use Illuminate\Broadcasting\PrivateChannel;
use Illuminate\Contracts\Broadcasting\ShouldBroadcast;
use Illuminate\Foundation\Events\Dispatchable;
use Illuminate\Queue\SerializesModels;

class UserRegistered
{
    use Dispatchable, InteractsWithSockets, SerializesModels;

    public $user;

    public function __construct(User $user)
    {
        $this->user = $user;
    }

    public function broadcastOn()
    {
        return new PrivateChannel(&#39;channel-name&#39;);
    }
}

We're passing the $user model to the event so listeners can access it.

Step 3: Write the Listener Logic

Open app/Listeners/SendWelcomeEmail.php :

 <?php

namespace App\Listeners;

use App\Events\UserRegistered;
use Illuminate\Support\Facades\Mail;
use App\Mail\WelcomeEmail;

class SendWelcomeEmail
{
    public function handle(UserRegistered $event)
    {
        Mail::to($event->user->email)->send(new WelcomeEmail($event->user));
    }
}

Make sure you have a WelcomeEmail Mailable:

 php artisan make:mail WelcomeEmail

Similarly, for logging:

 <?php

namespace App\Listeners;

use App\Events\UserRegistered;
use Illuminate\Support\Facades\Log;

class LogUserRegistration
{
    public function handle(UserRegistered $event)
    {
        Log::info(&#39;New user registered: &#39; . $event->user->email);
    }
}

Step 4: Register the Event and Listeners

Open app/Providers/EventServiceProvider.php .

In the $listen array, map the event to its listeners:

 protected $listen = [
    'App\Events\UserRegistered' => [
        'App\Listeners\SendWelcomeEmail',
        'App\Listeners\LogUserRegistration',
    ],
];

This tells Laravel which listeners should run when UserRegistered is dispatched.

After making changes here, run:

 php artisan event:cache

(for production; not required in local during development)

Step 5: Dispatch the Event

Now, trigger the event from your controller or model.

In your RegisterController or wherever user registration happens:

 use App\Events\UserRegistered;
use Illuminate\Support\Facades\Event;

// After user creation
event(new UserRegistered($user));

// Or using the Event facade
Event::dispatch(new UserRegistered($user));

Example in a controller method:

 public function register(Request $request)
{
    $user = User::create($request->validated());

    event(new UserRegistered($user));

    return redirect('/dashboard');
}

When this runs, both listeners will execute.

Optional: Event Discovery

If you don't want to manually register events in EventServiceProvider , Laravel can auto-discover them.

Enable it in EventServiceProvider :

 public function shouldDiscoverEvents()
{
    return true;
}

Laravel will scan the Listeners directory and auto-register event-listener pairs based on type-hinting in the handle() method.

Then you don't need to list them in $listen .

Run:

 php artisan event:cache

Best Practices

• Keep listeners focused: One job per listener.
• Use queueable listeners for slow tasks (like sending emails):

 class SendWelcomeEmail implements ShouldQueue
{
    use Queueable;
}

Make sure your listener uses the Queueable trait and implements ShouldQueue .

• Avoid heavy logic in events; use them just to signal.

Summary

Events and listeners help you write cleaner, more scalable Laravel apps by separating concerns. You've now:

• Created an event ( UserRegistered )
• Made listeners ( SendWelcomeEmail , LogUserRegistration )
• Registered them in EventServiceProvider
• Dispatched the event from your code

This pattern is great for audit logging, notifications, analytics, and more.

Basically, if something happens and other parts of your app need to know — use events.

以上是Laravel活動(dòng)和聽(tīng)眾教程的詳細(xì)內(nèi)容。更多資訊請(qǐng)關(guān)注PHP中文網(wǎng)其他相關(guān)文章！