-
Notifications
You must be signed in to change notification settings - Fork 11.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All Notification events should use SerializesModels #24350
Comments
Feel free to submit a PR. |
Submitted: #24368 |
taylorotwell
pushed a commit
that referenced
this issue
May 30, 2018
symfony-splitter
pushed a commit
to illuminate/notifications
that referenced
this issue
May 30, 2018
taylorotwell
pushed a commit
to illuminate/notifications
that referenced
this issue
Sep 17, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
All Notification events (
NotificationSending
,NotificationSent
,NotificationFailed
) should useSerializesModels
like BroadcastNotificationCreated does.Sometimes the
$notifiable
model has a bunch of extra stuff on it (relationships, etc) added during a flow and is being unnecessary added to queued jobs from the listeners. This has caused issues for our queueing system because the jobs can have huge payloads.Steps To Reproduce:
Send a notification using a notifiable with a lot of loaded relational data. See your queued listener jobs get huge.
The text was updated successfully, but these errors were encountered: