I am in the process of upgrading our project to LiveView 0.18. An interesting use case that has popped up is setting up a reusable live component for record forms that handle the Ecto changeset change validation and other boilerplate logic. This reduces the boilerplate by about 80-90%, but in my current implementation requires passing in function captures. The question is, is it an acceptable practice to “select” business logic in a template/component, or should I refactor this to require more boilerplate (probably closer to about 60% reduction) but have business logic purely handled in the parent live view’s handle_event? I could use handle_info as well, but that means that the logic is processed outside of the live event which breaks things like error handling and phx-disable-with.

Here is an implementation of my current approach:

<.live_component module={RecordForm} :let={f} for={@user} change={&Accounts.change_user/2} update={&Accounts.update_user/2}>
...
</.live_component>

So, Live View or Templates?