Due to the huge success and popularity of its predecessor, some client projects started using Angular 2 before its official release.
This resulted in Angular 2 becoming one of the most famous platforms for web and hybrid application development.
Although this framework is relatively new there are already a lot of tutorials and examples explaining how to develop an Angular 2 application.
However, there is one aspect of Angular 2 that is not widely covered, but is…
When I entered my current project one of the first things I noticed was it used stylesheet languages for its styles. "Yay!", I thought. But then I opened up one of those files and found nothing but plain vanilla CSS inside. It was the same for most of them. No nesting, no variables, no mixins, no inheritance, no operators… Well, you get the idea. I won't judge anyone and I'd rather believe those who wrote them didn't use them just because they didn't know how to. So I thought it would be interesting to write a short article explaining the basics of them. I could be explaining LESS instead of…
One of the cool things that we "were/are/will be" using while coding our front applications with AngularJs is the option to use directives to create our own reusable components. Basically, the main idea of the component was (...and is ...and will be) to have reusable elements that brings their own encapsulated functionality and also the ways to manipulate the data they need. If we were following the common known best practices, we were creating custom components by:
Why we get here? Apparently, we reach a point where we have met one of the bad parts of Angular (ng-repeat performance) and one of the good parts of React (virtual DOM).
Testing of Angular JS application used to be quite painful especially when using "official" solutions like Karma or Protractor.