Thanks for your reply. I feel like this is more of a "feature" than a bug in Angular. What other ways are there?
I guess my requirements are: - Access scope of directive with isolate scope from transcluded template - Access parent scope of isolate scope without going through tricky $parent routes that might break if you add more scope somewhere - Give an alias to something from the parent scope to inside of the isolate scope to get variable name independence inside the isolate scope directives controller and template What are the other ways to expose parts of the isolate scope that you mention? On Tuesday, June 24, 2014 7:28:38 PM UTC+9, Sander Elias wrote: > > Hi Sam, > > In the last beta there are quite some bug that have to do with > transclusion fixed. Did you try your use case with the last beta version? > However, there are more ways to expose (parts off) your isolate scope to > the transcluded scope. > I have to see some code to give some more precise advice on what is a good > solution in your case. > > 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.
