Open boptom opened 2 months ago
Hey, thanks for the in-depth explanation! I'll try taking a look at it today.
Hey! Unfortunately, I'm bereft of time lately and haven't had the opportunity to investigate what the root cause of this problem might be. I am most definitely welcoming pull requests that address this issue.
Thank you!
I'll give it another go when I have some time too. I'm not familiar with Laravel/Livewire internals and got lost following methods around last I tried.
I also couldn't figure out how to write a failing test for this. Any ideas?
I'll give it another go when I have some time too. I'm not familiar with Laravel/Livewire internals and got lost following methods around last I tried.
I also couldn't figure out how to write a failing test for this. Any ideas?
Hey, sorry for the late reply. You will most definitely need to set up Laravel Dusk for E2E testing since this is a visual hinderance which can only be observed on the browser.
The problem: When using Livewire redirect with
navigate: true
along with@persist
, the toasts do not show.In layout:
Docs on navigation here: https://livewire.laravel.com/docs/navigate#redirects Possibly related to: https://github.com/masmerise/livewire-toaster/issues/28
What happens: The page navigates, but the toast does not show.
What is expected? The page navigates and the toast shows "Toast Message".
Why not use regular redirects? Previous toasts are not persisted and disappear on navigation with regular redirects from the backend.
Why use @persist? To persist the toast messages through navigation.
Laravel: 11.5.0 Livewire: 3.4.11