3 ms·
Some of the 1.7 stuff has an alert banner that pops up when the connection is broken. I think that could really help. However I haven't put that in our app as
by eclark 4y ago
Some of the 1.7 stuff has an alert banner that pops up when the connection is broken. I think that could really help.
However I haven't put that in our app as I have seen other issues of flakey connection reconnect issues, and I would hate to make any of those more visible with a flashing notice.
- https://github.com/phoenixframework/phoenix_live_view/issues/2276 https://github.com/phoenixframework/phoenix_live_view/issues...
- https://github.com/phoenixframework/phoenix/issues/5102 https://github.com/phoenixframework/phoenix/issues/5102
- https://github.com/phoenixframework/phoenix/pull/5024 https://github.com/phoenixframework/phoenix/pull/5024
- dmix 4y ago> I would hate to make any of those more visible with a flashing notice. idk I haven't used LiveView in production but an interface that offers a well designed fallback "refresh" button helps for unpredictable edge cases, more so than the negatives of added complexity, which yes implies failure but is also certainly better than failing to optimize for reality. I ran into a similar hypothetical issues, that was really in practice an edge case, because we cached views for typical users. But I still provided a way to force reset of both server caches AND Localstorage caches because otherwise such an option was limited to advanced users/devs who either know backend or frontend. This is win-win ultimately because the user feels taken care of even in niche failure edge cases and QA/devs doing testing aren't forced to use exceptional means to reset state.