Deploying your application to multiple environments should be easy. But what if you are trying to maintain a 12 factor application? You have a requirement to generate a single build and promote that build up through the environments. Here is a great article for you if you are using Docker and want a strategy that will allow you to maintain 12 factor.
Teleporting isn't just for Captain Kirk. Beam your content to an entire new world.
What if we could enable children components to break through the limits of their own views, so, for them to display some of their widgets on a parent toolbar or pieces of information on a global status bar without data binding restrictions of any sort?
Understanding how to share data between components in a component based framework like Angular is obviously really important. And we're not talking about a state management library here. Just the basics of @Input(), @Output(), and @ViewChild.
But still today, I sometimes look at the syntax of the import statement and do a double take. Just when I start getting used to what the curly braces are doing, suddenly there’s an asterisk, or even nothing at all. Why are there so many variations going on?
If you're like me, you probably see your fair share of *ngIf in your code base. This article is a great reminder that there are other flavors of ngIf. ngIfThen and ngIfElse. See how you can use these options in your templates to make more dynamic interfaces.