You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: resources/docs/notifications-and-events.md
-52Lines changed: 0 additions & 52 deletions
Original file line number
Diff line number
Diff line change
@@ -232,58 +232,6 @@ We've used a [database cursor](https://laravel.com/docs/eloquent#cursors) to avo
232
232
> **Note**
233
233
> In a production application you should add the ability for your users to unsubscribe from notifications like these.
234
234
235
-
### Registering the event listener
236
-
237
-
Finally, let's bind our event listener to the event. This will tell Laravel to invoke our event listener when the corresponding event is dispatched. We can do this within our `EventServiceProvider` class:
* Determine if events and listeners should be automatically discovered.
278
-
*/
279
-
public function shouldDiscoverEvents(): bool
280
-
{
281
-
return false;
282
-
}
283
-
// [tl! collapse:end]
284
-
}
285
-
```
286
-
287
235
## Testing it out
288
236
289
237
You may utilize local email testing tools like [Mailpit](https://github.com/axllent/mailpit) and [HELO](https://usehelo.com/) to catch any emails coming from your application so you may view them. If you are developing via Docker and Laravel Sail then Mailpit is included for you.
0 commit comments