We've talked about one way data binding and two way data binding.
Now there is another way of data binding, which is called the one time data binding, which is a little
bit simpler than those two.
So for one time data binding, let's just write down one time as the name already suggests.
It just updates the data for a single time.
And this is useful for anything that's related to configuration or constants.
So things that don't change usually.
So if you want to load any, let's say, configuration, you could just start your application set up
one time data binding and then like we got that in our data source.
So Yannick and 30 right here, this is bound a single time.
But whenever I would now go ahead and update the person right here, it would not get reflected.
The element would not get changed, the user interface element because it just got bound a single time.
So keep in mind, whenever you want to load any constants or configurations, anything that's kind of
static and only well does not change, but you want to reflect it in the UI.
A single time.
You can use the one time data binding.
Don't get confused.
There is one way data binding and one time data binding and in one time data binding we only bind or
reflect the data a single time.