It's just occurred to me that obviously the only front end that can use real time notifications right now (without reloading or navigating) is Livewire but Laravel has broadcasting that can be used to have real time notifications without reloading (for example doing actions on the back end that don't change page content like sending a password reset email to a user from a dashboard).
I can make support for all the Laravel broadcasting drivers (Reverb, Pusher, Ably) as I need an excuse to work with them but just wondered whether you think this is within scope? @limonte
I 'll draft the implementations and then consult about how to work it into the existing method signatures.
For Livewire I think we just stick to using Livewire's dispatch as adding extra overhead doesn't make sense but for Inertia and plain Laravel I think it would be really helpful to have real time notifications without having to use Livewire.
It's just occurred to me that obviously the only front end that can use real time notifications right now (without reloading or navigating) is Livewire but Laravel has broadcasting that can be used to have real time notifications without reloading (for example doing actions on the back end that don't change page content like sending a password reset email to a user from a dashboard).
I can make support for all the Laravel broadcasting drivers (Reverb, Pusher, Ably) as I need an excuse to work with them but just wondered whether you think this is within scope? @limonte
I 'll draft the implementations and then consult about how to work it into the existing method signatures.
For Livewire I think we just stick to using Livewire's dispatch as adding extra overhead doesn't make sense but for Inertia and plain Laravel I think it would be really helpful to have real time notifications without having to use Livewire.