I'm just curious here about the choice of { something & propToModify = fooBar }
Why not use javascript style syntax of {...oldModel, someProp = someThing }
Would also allow for updating nested data more easily, which for me, has always been a painpoint in Elm that needs multiple steps of local variables.
Maybe good reasons to avoid this syntax?
we want to have { oldModel & foo.bar: fooBar }
already, not sure what advantages JS syntax would bring beyond that
Folkert de Vries said:
we want to have
{ oldModel & foo.bar: fooBar }
already, not sure what advantages JS syntax would bring beyond that
I wasnt aware of that! Thanks @Folkert de Vries
Oliver Schöning has marked this topic as resolved.
Last updated: Jul 06 2025 at 12:14 UTC