No problem at all. There may be another way to do it without hiding fields but I’m not sure since we want every field param sent to handle_event("validate"... on each keystroke (or after x milliseconds or onBlur if you set the debounce) so you can feed them all to the changeset. Also you want every field sent to your “save” event.
In order to figure out how it all worked I had to use IO.inspect() a lot to study the %Changeset{} struct and %Form{} struct and how they change in response to events calling the related functions in the modules.
Also, I was looking at your Order module and not sure if you want to persist this as a DB table but you may want to use Ecto.Schema here instead of relying on schemaless changesets since right now it validates but doesn’t persist. A good pattern for LV forms can be found in the official examples here: LV Form Examples where in the handle_event("save"... you simply call the context function to persist (which validates it again) then pattern match on the result. If it’s {:ok, user} then it worked and you redirect with flash but if {:error, changeset} is returned then you can display the errors.
Hope this helps!
I’ll try to undelete the post when the action wait period is over.