Menu Search
Jump to the content X X
SmashingConf London Avatar

We use ad-blockers as well, you know. We gotta keep those servers running though. Did you know that we publish useful books and run friendly conferences — crafted for pros like yourself? E.g. our upcoming SmashingConf London, dedicated to all things web performance.


Nico is an enthusiastic JavaScript hacker based in Buenos Aires, Argentina. When he's not hacking away at freelance projects, or contributing to the open source community as @bevacqua, Nico spends time writing content for Pony Foo and devoting time to local communities such as NodeSchool and NodeBots as well as Beer.js; and he’s published a book, named JavaScript Application Design.

Twitter: Follow Nicolas Bevacqua on Twitter

Google Profile:

AngularJS’ Internals In Depth, Part 2

In the previous article in this series, I discussed scope events and the behavior of the digest cycle. This time around, I’ll talk about directives. This article will cover isolate scopes, transclusion, linking functions, compilers, directive controllers and more.

AngularJS' Internals In Depth, Part 2

If the figure looks unreasonably mind-bending, then this article might be for you. This article is based on the AngularJS v1.3.0 tree.


AngularJS’ Internals In Depth

AngularJS presents a remarkable number of interesting design choices in its code base. Two particularly interesting cases are the way in which scopes work and how directives behave.

AngularJS' Internals In Depth

The first thing anyone is taught when approaching AngularJS for the first time is that directives are meant to interact with the DOM, or whatever manipulates the DOM for you, such as jQuery (get over jQuery already!). What immediately becomes (and remains) confusing for most, though, is the interaction between scopes, directives and controllers.


↑ Back to top