We basically hide a new state for the transitioning values so manual comparisons in shouldComponentUpdate (without considering the hidden state) would return the bad result during transition (aka not updating when we need to update). Wouldn't be a problem with a deepCompare(state1, state2) function, except js doesn't have it by default so people don't do that.
Closing. As long as we stick with mixins, this will be the case. ClojureScript folks have it easy since they can just compare the whole prevState and this.state using the efficient deep compare.
We basically hide a new state for the transitioning values so manual comparisons in
shouldComponentUpdate
(without considering the hidden state) would return the bad result during transition (aka not updating when we need to update). Wouldn't be a problem with adeepCompare(state1, state2)
function, except js doesn't have it by default so people don't do that.