Ember.js: Rendering aliases break when rendering a CP dependent on them
Update: it doesn't have to do with yield, or attrs, it is just the order of rendering (ref consumption) and whether the CP is rendered (ref consumed). Updated fiddle: https://ember-twiddle.com/9f5a189ebe41a8191c1b280ce80592a1
Under Ember 2.10, when a component yields a property defined with computed.readOnly, under certain circumstances in production builds of Ember only, downstream usage are not updated when the property changes.
I worked with @krisselden to created an isolated reproduction of this issue:
The reproduction demonstrates that the order that the attributes are passed into a consuming component determines which property fails to update. o_O
lukemelia
All 3 comments
Kris' hypothesis in our discussion is that there is a race in how AliasProperty (which readOnly uses) adds its dependent key and the consumption of the property, and that something in the development build papers over the bug.
lukemelia
on 2 Dec 2016
It seems to be that consuming the CP breaks rendering of the dependent keys if they are aliases https://ember-twiddle.com/9f5a189ebe41a8191c1b280ce80592a1
krisselden
on 3 Dec 2016
@lukemelia this was fixed in 2.10.1 😄
chancancode
on 15 Dec 2016
Related issues
dfreeman
·
4Comments
mar20
·
4Comments
nathanpalmer
·
3Comments
hilem
·
4Comments
rafaelbnp
·
3Comments
Most helpful comment
@lukemelia this was fixed in 2.10.1 😄