"You modified ... twice in a single render" deprecation warnings

[jamesarosen]

Running on Ember 1.13, I get the following deprecation warnings about modifying a property twice in a single render:

• graphHeight due to xAxis
• graphWidth, due to yAxis
• [d] for unknown reasons

I tried changing some of the components' init hooks to didInitAttrs, but that breaks because their parent components expect them to exist during initialization.

See also emberjs/ember.js#11156

[zkwentz]

Brace yourself, this will be redundant but it's worth laying out exactly what's happening.

The nf-graph renders, yields to it's block. In that block, we have our nf-(xy)-axis, when that axis is initialized it sets itself on the nf-graph component. The nf-graph component has a computed property for graphHeight and graphWidth. One of the dependentKeys is the height of the nf-(xy)-axis. The timing of this, is such that, when the nf-(xy)-axis is initialized, the nf-graph is mid-render. The graphHeight recomputes, and the height={{graphHeight}} in the nf-graph template changes, raising the deprecation warning.

[benlesh]

Yeah, this is a biproduct of having the scales contained at the nf-graph level, and not defined by the nf-(xy)-axis components, which is probably where they should be.

I'm open to any solution that can be provided. We're still stuck on Ember 1.11 - 1.12 on our apps on my team at Netflix because of other deprecation issues and breaking changes, so I haven't seen this since I tried (and failed) to upgrade to 1.13.