בפוסט זה (אני מאמין שגם הבאים אחריו ) אני רוצה להציג לכם את אנגולר 2 “מתחת למכסה המנוע”. החומרים אלו גם משמשים אותי לקורס שאני עובד עליו בימים אלו :Course Angular 2.0 for Angular 1.x Developers.השאלה שאני אנסה לענות אליה בפוסט זה היא, איך עובד מנגנון זיהוי השינויים החדש של אנגולר ובמה הוא שונה מה- digest של אנגולר 1?
This article has been update in October 14th. Now it is using TypeScript and angular 2.0.0-alpha.42 Note: If the “foo” alerts from the …
Angular 2 is around the corner and there are mixed opinions about it. Some people can’t wait for it and other people are not any happy with it. Why is that? People are afraid to change, thinking that they wasted their time learning something that is now going to change in a radical way.
One of the hottest topics when it comes to Angular 2, is how to get our existing AngularJS applications upgrade to the next major version of the framework. The APIs of Angular 2 are stablelising and a module to help upgrading existing AngularJS apps is emerging. This module is called ngUpgrade and in this article we’re going to explore what comes into play when upgrading an app and also how ngUpgrade gives us a helping hand.
When writing Angular 2 applications, it often happens that we build services that depend on other service instances. In our previous articles, we learned about the Dependency Injection system in Angular 2 and how it works. However, it turns out that we might run into unexpected behaviour when injecting service dependencies. This article details how to do it right.
Angular 2 has been rewritten from scratch to take advantage of a lot of new technologies that are coming to the web. One of those technologies are Web Components. In fact, Web Components is a set of four technologies: HTML Imports, Templates, Shadow DOM and Custom Elements. Angular uses templates for structural DOM changes, and Shadow DOM for styles and DOM encapsulation. This article explores Angular 2’s view encapsulation and how we can use it.
Source: View Encapsulation in Angular 2