Hi Sam, Well, a large part of it is a "feature" indeed. but along the way, there was some quirky behaviour in there too. Have a look at the 1.2.18 changelog <https://github.com/angular/angular.js/blob/master/CHANGELOG.md#bug-fixes-2>, (hmm, the stable release got some of those too!) and the 1.3.beta-11 log <https://github.com/angular/angular.js/blob/master/CHANGELOG.md#bug-fixes-3> .
Are you sure you are going to need this? Most of the time, there is a more easy way to work around a lot of those issues that are related to this. One of the more simple ways to accomplish it, is expose the controller of the directive with the controllerAs property. You can then link the isolate scope to to the controller of the directory. have a look at this sample <http://goo.gl/J1ANqq>, on how to expose an controller. You can extend this to a directive with an isolate scope. (BTW the sample is just to show how to expose an api, not a text-book example of angular use!) If you are going to mix in the transcudeFN in the mix, you can create anything with any scope you want. However, as I said before, while this will work, it is in most circumstances not the best path to a solution. So, if you can give me a code-sample of what you are aiming for, I can perhaps give some more solid guidance! Regards Sander -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
