Wrong nodes referenced with multiple sibling/child template controllers on surrogate elements

[aurelia]

Wrong nodes referenced with multiple sibling/child template controllers on surrogate elements

[fkleuver]

@ghiscoding Hey :) if this was indexed assignment you would have been correct, but here I'm reassigning a new array instance (thus completely replacing the old one). The observation side of things works as it should.

Perhaps interesting to note, that now we have things like proxies we might be able to support even observing indexed assignment. We'll be looking into that some later point in time.

In any case, the mutation is registered correctly because in the debugger I could see the repeater attempting to remove the views. But the logic that removes the views ends up removing the wrong nodes from the DOM.

[ghiscoding]

@fkleuver
Could that be a binding issue with a mutation (assignment) that Aurelia cannot see? I had a similar issue and asked on SO here in which Jeremy Danyow replied:

Aurelia observes changes to the contents of an array by overriding the array's mutator methods (push, pop, splice, shift, etc). This works well for most use-cases and performs really well (no dirty-checking, extremely lightweight in terms of memory and cpu). Unfortunately this leaves one way of mutating an array that aurelia can't "see": indexed assignment... eg myArray[6] = 'foo'. Since no array methods were called, the binding system doesn't know the array changed.