Angular 2 has landed! Rejoice! After 18 beta releases and 8 release candidates, the final version saw the light of day in September and you can now consider it stable enough to use it. It’s a totally different framework when you try to compare it with 1.x but the principles are the same. You get the proper tools to build your web application from the UI to the data retrieval and everything in between. The plan is to have multiple quick tips appear here as I play with it. To start this process I will try to explain one of the concepts that took me a while to grasp once I started migrating one of my applications to Angular 2, the module system!
Category: Quick Tips
Dependency injection is your friend when you want your code to be testable and if you work with Angular you know that this is a fundamental concept. Angular 2 will be developed with TypeScript but if you want type safety you can use TypeScript with Angular 1.x today as well. When it comes to DI with Angular and TypeScript, you can do some pretty nice stuff.
Libraries and frameworks like Angular.js will make things easier for you and provide you with a clear way to design your code but you have to respect its rules. Naming element directives properly is one of the very important rules.
The module concept in Angular.js is something that you love when you’re one of these developers who don’t like having global variables in your application. I’m one of these guys. It works by letting you define angular modules and then you can include objects in these modules based on what their functionality is. For example you might want to have a module for all your network services, another for your directives, another for your controllers and so on. Defining these modules and accessing them later from some other part of your code might be a bit confusing because the syntax differences are minor. This tip is all about these two functions in Angular.