Is there a reason you'd do it this way rather than making a custom directive with an isolate scope?
On Tue Dec 02 2014 at 8:18:38 AM Kranthi Kiran <[email protected]> wrote: > adding an ng-if="'true'" inside the ng-include directive did the trick for > me. I guess ng-if creates a new scope for the containing element. > > In your case, the code would look like - > > <ng-include src="'partials/addressform.html'" onload="type='billing';" > ng-if="'true'"></ng-include> > <ng-include src="'partials/addressform.html'" onload="type='delivery';" > ng-if="'true'"></ng-include> > > -- > 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. > -- 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.
