If you talk about explicitly updating each level then yes, that's still the
best approach.
You break your models into components and update each component as per Elm
Architecture.
If you talk about Focus, then no, I have not seen that really used.
you could do update functions like this:
updateLeftX x ({left} as model) =
{ model | left = {left | x = x} }
but it is better to have something like
updateLeftX x model =
{ model | left = Point.updateX x model.left}
On Mon, Jul 18, 2016 at 8:40 PM, Jesse Schoch <[email protected]> wrote:
> Is this still the best way to deal with nested record updates?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Elm Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
--
There is NO FATE, we are the creators.
blog: http://damoc.ro/
--
You received this message because you are subscribed to the Google Groups "Elm
Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
