📎 Webclip
Phoenix LiveView: Multi-step forms
The post says Phoenix LiveView makes it practical to move common front-end logic into the backend, especially for long or multi-step forms. The author contrasts a single large LiveView form with a component-based approach, where each step owns its own state and computed fields.
Reading notes#
- LiveView is presented as a good fit for consolidating front-end logic in the backend, especially for long-running or multi-step forms.
- The first attempt used one large LiveView and one
<form>for every step, with hidden sections shown one at a time. - That approach caused problems with Enter submitting too early, state from other steps still needing management, validations affecting hidden inputs, and difficult testing.
- The author also needed computed fields such as dates, times, time zones, and duration, which made the single-form approach harder to reason about.
- The recommended structure is to split the form into LiveComponents, with embedded schemas as form objects for each step.
- The parent LiveView keeps a
%Step{}structure and a step order list, and switches the visible step when components send messages back. - Each component initializes its changeset from the record, validates user input locally, computes derived values, and sends the finished struct upward when valid.
- The
WhenComponentexample stores timezone, date, time, and computed fields such asstart_at,end_at, andduration. - The component updates computed values after validation and on load, so the parent can combine step params into the final record later.
- Browser timezone is detected with
Intl.DateTimeFormat().resolvedOptions().timeZoneand passed into the component through aphx-hook. - The hook updates a hidden input and immediately pushes a
timezoneevent to the LiveComponent so the changeset can be updated before user interaction. - Validation events are targeted at the LiveComponent with
phx-target, and the component adjusts time params whenstart_at_timeorend_at_timechanges. - On submit, the component uses
Ecto.Changeset.apply_action/2to confirm validity and then sends the completed struct to the parent LiveView. - The parent LiveView merges the step data into accumulated params, advances to the next step, and saves once there is no next step.
- The conclusion notes that drafts between steps could be persisted with
handle_params, and that the code is written for creating a new event rather than editing one.
