I want to quickly into the issue, another topic that is the energy container directive.
If you go to the browser and play and you wait until the countdown ends, then it will show the alert
and you can.
Right click and inspect this element.
As you can see, it is an absentee ballot view.
And inside there's a deep element with the whole alert content inside it background the card with the
header message and so on.
This outer dip is doing nothing.
I only use it to grab the content of the alert and use the energy in order to include the content in
the them when the visible property equals through.
Let me show you the simple order to be a template so you can see what I'm talking about.
Untap.
I have this deep element with the energy.
If they are active, that's the only reason of this dip.
It is more efficient to grab all those aliment and the one only endive directive then using NGF on every
one of the internal elements.
However it atsumi anextra and the necessary node in my thumb.
This is a perfect example of the energy container usage and the container is a natural directive that
works as a larger container.
It allows you to group nodes, but without an annoying extra not wrapping them because it does not render
itself on the dump.
Let's put it on practice.
I replace this outer DB element by an empty container and of course I have to change also the closing
deck and the container.
OK, I save this and I'm off to the browser and the same as before, I click play.
I wait until the alert appears and then when I inspect it, you can see that inside my app, Simple
View, I directly have the internal elements, background and cats.
Now, there is not an intermediate node grouping.
All this content from here, thanks to engine container, I have managed to group the elements with
a single engine if but I have avoided an overload of the them with an unnecessary node.