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
{{ message }}
This repository has been archived by the owner on Sep 7, 2021. It is now read-only.
@RemiCollin little to none except it makes a much more clear structure for delivery. It separates the who, what and where into notifiable, notification and channel. You can easily do the same thing with dispatching a job but then if you want to change or expand on that job you'll end up creating another job to sit along side the other. I'm sure there will be a few pros and cons for both ways tbh.
I just know I like using custom Channels to solve a few problems like that.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
https://medium.com/@SlyFireFox/laravel-innovations-making-your-own-webhook-mechanism-through-notifications-96e75e99a2b1
The text was updated successfully, but these errors were encountered: