[BUG] arrayComputed does not recalculate after dependant array is set

[wongpeiyi]

Here is a failing test case: http://jsbin.com/dohavimi/1/edit?html,js,console

Basically, computed.filterBy or computed.filter fails to recompute synchronously after its dependant array is set. An explicitly defined computed property works, so it looks like an arrayComputed issue. It works if their values are not cached (if you remove the prior gets). It also works if I use pushObjects instead of set.

Am I wrong to assume the computed properties should recalculate synchronously before the final gets?

[mmun]

The recalculation of ArrayComputed doesn't have the same semantics as ComputedProperty. computed.filter and computed.sort schedule their recalculation on the run loop. Your example will work if you put the gets in another Ember.run.next.

[wagenet]

@mmun do you think we can fix this? or should we just close?

[drogus]

The recalculation that @mmun mentions happens here. It seems that it could be removed once compound dependent keys, which are mentioned in #5268, are implemented.

[wagenet]

@mmun ping.

[mmun]

@ef4 do you have any thoughts on this matter?

[ef4]

This behavior is definitely undesirable. Ideally we would separate the invalidation step from the recomputation step. That's how scalar computed properties work.