A Look into AngularJS Compilation Process
Angular's HTML compiler allows you to teach the browser new HTML syntax. The compiler allows you to attach new behaviors or attributes to any HTML element. Angular calls these behaviors as directives.
AngularJS compilation process takes place in the web browser; no server side or pre-compilation step is involved. Angular use
$compiler service to compile your Angular HTML page. The angular' compilation process begins after your HTML page (static DOM) is fully loaded. It happens in two phases :
It traverse the DOM and collect all of the directives. The result is a linking function.
It combine the directives with a scope and produce a live view. Any changes in the scope model are reflected in the view, and any user interactions with the view are reflected in the scope model.
The concept of compile and link comes from C, where you first compile the code and then link it to actually execute it. The process is very much similar in AngularJS as well.
Comparing Angular template compilation with other framework template compilation
If you have worked on templates in other java script framework/library like backbone and jQuery, they process the template as a string and result as a string. You have to dumped this result string into the DOM where you wanted it with
AngularJS process the template in another way. It directly works on HTML DOM rather than strings and manipulate it as required. It uses two way data-binding between model and view to sync your data.
How angular's directives are compiled
It's important to note that Angular operates on DOM nodes rather than strings. Usually, you don't notice this because when a html page loads, the web browser parses HTML into the DOM automatically.
HTML compilation happens in three phases:
The $compile traverses the DOM and looks for directives. For each directive it finds, it adds it to a list of directives.
Once the entire DOM has been traversed, it will sort that list of directives by their priority. Then, each directive’s own compile function are executed, giving each directive the chance to modify the DOM itself. Each compile function returns a linking function, which is then composed into a
combinedlinking function and returned.
$compile links the template with the scope by calling the
combinedlinking function from the previous step. This in turn will call the linking function of the individual directives, registering listeners on the elements and setting up $watchs with the scope as each directive is configured to do.
The pseudo code for the above process is given below:
var $compile = ...; // injected into your code var scope = ...; var parent = ...; // DOM element where the compiled template can be appended var html = '<div ng-bind="exp"></div>'; // Step 1: parse HTML into DOM element var template = angular.element(html); // Step 2: compile the template var linkFn = $compile(template); // Step 3: link the compiled template with the scope. var element = linkFn(scope); // Step 4: Append to DOM (optional) parent.appendChild(element);
What do you think?
I hope you have better understanding of AngularJS compilation process. I would like to have feedback from my blog readers. Your valuable feedback, question, or comments about this article are always welcome.