-
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
[5.6] Allow notification routing to depend on notification being sent #22289
[5.6] Allow notification routing to depend on notification being sent #22289
Conversation
Couldn't this be considered breaking because you changed the signature of a public and protected functions that may have some effect? |
Merged into 5.6. One question I do have is when would the notification ever be |
The notification will never be |
Change log is pointing to 5.5. :/ |
@freekmurze I was just about to open a PR for the same exact thing. Found your Laracasts thread, and found you'd already done it! Thanks! |
Maybe this breaking change should reflect in the upgrade guide to 5.6 |
This adds support for the feature added in Laravel 5.6 for routing based on the notification being sent (laravel/framework#22289).
This adds support for the feature added in Laravel 5.6 for routing based on the notification being sent (laravel/framework#22289).
This PR makes notification routing a bit more flexible by passing the notification to the
routeNotificationForXXX
If this would be accepted, this would become possible:
Didn't yet figure out how the new behaviour can be tested properly.