3 ms·
With pure LiveView, I would agree, but you can easily supplement with a JS framework. As I mentioned above: > You can also use the built-in JS module to do cl
by freedomben 4y ago
With pure LiveView, I would agree, but you can easily supplement with a JS framework. As I mentioned above:
> You can also use the built-in JS module to do client-side things when you don't need backend support. I use Alpine.js (PETAL stack) and I like it a lot.
If you have a very complex client-side need, it's also pretty easy to use React.js for that.
While you could, I never use LiveView to open dialogs (unless the dialog state needs to be distributed across multiple clients, but I haven't had that use case come up yet). As you mention, that would lead to a poor UX.
The best is the best of both worlds. LiveView for data/state changes that need to go to the database, client-side script for state changes that are UI related and don't get persisted.