Observing array using array.[] is not working in v1.13.11

[devinus]

Reproduced here: http://ember-twiddle.com/b663e28c60942f4c3d25

[stefanpenner]

nothing appears to be consuming allValues doing so makes everything work. This appears to be working as expected?

[stefanpenner]

also 'allValues', 'allValues.[]', is redundant as observing 'allValues.[]' is a superset of 'allValues'

[devinus]

@stefanpenner valuesDidChange is consuming allValues.

[devinus]

Is this a case of too aggressive optimization? I have an observer observing a computed property, is that not enough to trigger a consumption?

[devinus]

A simpler example: http://ember-twiddle.com/b663e28c60942f4c3d25

[stefanpenner]

@stefanpenner valuesDidChange is consuming allValues.

yes, but valuesDidChange only fires, if allValues has already been consumed and then changes.

[devinus]

@stefanpenner So, the takeaway is you cannot observe a computed property unless that computed property is consumed elsewhere?

[stefanpenner]

@stefanpenner So, the takeaway is you cannot observe a computed property unless that computed property is consumed elsewhere?

Yes correct, think of them as Schrödingers Computed Properties. Before consumed, the state is undefined, and as such no state change notification is possible.

The laziness invariant is actually quite nice, but results in the single caveat we just discussed.

[devinus]

@stefanpenner So what's the correct way to do this then? Am I going to have to <div class="hidden">{{allValues}}</div> to get this to work?

[stefanpenner]

@devinus or you can call this.get('values'); // force eagerness of CP in init() after _super()