These are chat archives for jdubray/sam
store.temperature.air, and the other at
store.temperature.water. But the component only needs to work with
receivefunction. The "form" component manages the root model.
model.units. Now, here is where the higher-level form component creates two instances of the temperature component and nests their models at
@jeffbski What is the difference between:
var m = new Model(); m.accept(proposal).then(access)
access(m = accept(m, proposal))
There might be some legitimate cases for making some part of the model "immutable", because they are truly immutable but there reality is that the whole point here is to mutate application state, one way or another.
The biggest issue I have with Redux/immutability is that it conflates proposers and acceptors and assignments with mutation. There is tremendous benefits in deconflating proposers from acceptors and assignments from mutation.
How does immutability help with that goal?