I hear conflicting recommendations on this. Some people feel that isolate scope should be used for all "reusable" directives where reusable means that it will be used in multiple applications and multiple parts of the same application. The reasoning I hear is that it avoids depending on the data in the scope of where the directive is used and provides a clean contract for what data must be provided to the directive. This makes directives somewhat similar to pure functions in functional programming where everything they need is explicitly passed to them.
If you take this view then it seems that isolated scope would be used quite often. Why do you say this is rare? --- R. Mark Volkmann Object Computing, Inc. > On Feb 2, 2014, at 9:15 PM, Sander Elias <[email protected]> wrote: > > Hi Alexander, Andrei, > > Ok, This is a put a bit simpler as it really is, but aside of some edge > cases, this explanation will hold. > This doesn't work as an isolated scope is isolated to the directive, not to > its element. And yes Alexander, that includes it's templates. > One seldom really needs isolated scopes. There is use for those, but that is > a rare condition. > > 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/groups/opt_out. -- 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/groups/opt_out.
