In this article, I describe a beautiful form abstraction I discovered while playing with my form fields.
I’d be happy to receive stories or examples of forms you found quite challenging to build with the current form abstractions that the Elm ecosystem provides.
What do you think is difficult about forms that I may have overlooked?
I’ve chatted a fair amount with @edkelly303 about elm-any-type-forms 8.1.0, and something I asked him once was
whether it is possible for the state of a field to depend on the state of another field.
I don’t really remember asking, but I think I know the context. When I worked at Northwestern Mutual I worked on a large, complex form that had a crazy group of fields. It was 2 currency inputs and a slider. When you edited any 1 of the 3 fields, the other 2 would also update. It was about having the 2 currency fields equal a total and the slider match up as well.
That’s up there with some of the most challenging form stuff I’ve encountered.
Thanks for the example. My approach would handle that requirement in setters.