fix(ElementBinderBuilder): throw if more than one transcluding directive...

[vicb]

... per node

fixes #1306

[chirayuk]

This change has been reverted in 2b0d9de.  It breaks a bunch of apps that do something like:

<foo ng-if="isEnabled" ng-repeat="item in items">

which just happens to work today.  Folks, including me, need more time to fix some large apps that break.

I've moved this onto our staging branch for early merging.

It might actually be a good idea if we can have this be split into two commits – the first one deprecating this change and the next one actually throwing the exception.  I think di and some other changes were made this way where we would throw a warning in the console (and suppress repeated warnings) in the console first and the next version would make it an error. Would you like to take on this task and write this in a more backwards friendly way?

[vicb]

@chirayuk check #1374, I don't think this works today (as explained in the issue linked in 1374). Then I think throwing is the right thing to do as the code is broken anyway.

[jbdeboer]

+1 to @chirayuk's comments. Let's do this in two phases.

Also, the common use-case of <div ng-if ng-repeat> seems useful.