@ctusch wrote:
When you bind to a value of a child component (using
viewName
) or when you observe that value in one of your properties you get the following deprecation warning:
DEPRECATION: You modified childComponent.prop twice in a single render. This was unreliable in Ember 1.x and will be removed in Ember 3.0 [deprecation id: ember-views.render-double-modify]
`I was able to reduce my problem to this code. Although in my real application I have a computed property depending on
childComponent.prop
which causes the same warning.prop
is not part of the model.I guess I could have an action that fires every time the value changes. But I think this should work or why else does
viewName
exist? Is this a bug?
Posts: 2
Participants: 2