Angular “Two-Way” Binding

Share This Post

In the previous several posts, we have looked at three types of binding (interpolation, property and event). In interpolation and property binding, the communication flows one way…from class to template. That direction when combined with Angular’s change detection allows you to programmatically update the class and change information that then gets updated in the template view. In event binding, the communication flow comes from the template to the class. In other word, when the end user triggers an event, then some method runs. But what about two-way? Angular provides what I, personally, call quasi-two-way binding. Two-way binding can be achieves by combining property and event binding with the “banana in a box” method.

Angular provides a directive (ngModel) to achieve two-way data binding. You start with importing the FormsModule and then you can create your two-way binding with ngModel as follows…imagine you have the following class…

export class AppComponent {
    dessert = 'chocolate ice cream';

We can set up two way data binding with form inputs as follows…

<!-- input for user to provide their own dessert -->
<input type="text" [(ngModel)]='dessert'>
<!-- the end users dessert will display here -->
<p>My favorite dessert is {{dessert}}</p>

The special notation using [(ngModel)] is called the “banana in a box” notation. I guess because someone thought that the parentheses looked like a banana and the square brackets look like a box…I dunno. But it combines property and event binding notation. So whenever the end user updates the input, the dessert property gets notified and changed, then the template view gets updated.

Happy Coding!

Clay Hess

More To Explore


Demystifying Scrum User Stories Confirmation: Ensuring Quality and Collaboration

One of the key elements of Scrum is the use of user stories to define the requirements of a system or feature from the perspective of the end user. As teams work through the product backlog, it becomes crucial to confirm the user stories to ensure they meet the desired criteria and are ready for development. In this blog post, we’ll explore the concept of Scrum user stories confirmation and its significance in delivering high-quality products.


The Power of Conversations in Scrum User Stories

At the heart of Scrum lies the concept of user stories, which serve as a means of capturing requirements from the perspective of end-users. However, the true power of user stories lies not just in their written form but also in the conversations that take place around them. In this blog post, we will explore the significance of conversations in Scrum user stories and how they contribute to the success of Agile projects.

Do You Want To Boost Your Business?

drop us a line and keep in touch

Scroll to Top

Need help?

Let's have a chat...


Jump Back In!

Here at Webolution Designs, we love to learn. This includes sharing things we have learned with you. 


Begin Your Learning Journey Today!

Come back inside to continue your learning journey.