Can't we get @each to support deep properties?

[simonexmachina]

Having a property dependency on [email protected], doesn't work. You need to define barQuzBinding: 'bar.quz'. Can we can get @each to handle this transparently? Or at least throw an exception if a deep property is used.

[mixonic]

@aexmachina I think an exception or assert would be best. Deep chaining of observers can perform poorly. We're building Ember 2.0 around the idea that you won't need deep observation in new codebases.

[mmun]

Our goal is to flesh out the diffing story so that you never need to use @each again, let alone nested @each!

[simonexmachina]

Awesome, that sounds great. But I think right now it should throw an exception so people know that it's not supported.​

[mmun]

Agreed.

[archaeron]

yes please 👍

[wagenet]

I remember trying to get an assertion in for this a long time ago. It was a huge pain in the butt then and I gave up. I'm not sure if it will have gotten any easier.

[endash]

If difficult to impossible to get an assert in-line, maybe a grep-based warning on build would suffice?

[stefanpenner]

should throw an exception if it isn't supported, as to not confuse users

[rwjblue]

Was talking to @krisselden about this the other day. The recent refactor (for 2.0.0) for @each will unlock the ability to support [email protected].

[rwjblue]

Helpful warning added in #12847.