I could also see the log output being reasonable. But that gets at the
question behind the question, which is this: How can I observe a change
caused by an actual edit of an item of the list, and not a reassignment of
the data objects to the element instances that is causes by things like
Not sure if it is the intended behavior or not, but I wouldn't find it hard
to believe that the change observer fires since the index of each element
changes as you unshift into the list array...
essentially: list[0] becomes list[1] meaning previous[1] != list[1]
effectively causing a series of
I have posted this in another form on SO
(http://stackoverflow.com/questions/42565640/how-to-distinguish-between-structural-changes-to-array-made-in-parent-element-vs)
and in the 2.0-preview branch slack channel, but I know they are heads down
with the upcoming release, so hopefully somewhere