new-event-listener

To hook into Forge model lifecycle events, you implement an EventListener with a handle method and register it in a service provider. This automates cross-cutting reactions to generic ModelCreatedEvent, ModelUpdatedEvent, and ModelDeletedEvent without embedding logic in models.

The best way to listen to multiple domain events is using a multi-event listener. You register it via registrar.listen_event in your service provider, allowing a single listener to handle several target events and trigger corresponding side effects.

Yes, you can trigger custom side effects by defining a custom domain event type, implementing an EventListener to handle it, and wiring the listener in the EventServiceProvider. This decouples reactions like jobs or audits from core model logic.

You need a container-resolving listener when your event handler requires dependency injection. Registering this listener type via the service provider allows the event bus to resolve necessary services from the container automatically during event handling.

Event listeners keep cross-cutting actions separate by reacting to emitted domain events externally. Instead of placing audit or email logic inside models, you register listeners in a service provider to handle events like UserRegistered independently.