Two-way binding in forms in Angular

Introduction

Two-way binding lets your form inputs and your app data stay in sync automatically. When you change the input, the data updates, and when the data changes, the input updates.

You want to update a variable as the user types in a text box.

You want to show the current value of a variable inside a form input.

You want to keep form data and your app state connected without writing extra code.

You want to build interactive forms that react instantly to user input.

Syntax

Angular

<input [(ngModel)]="propertyName" />

Use [(ngModel)] inside form elements to bind data both ways.

Make sure to import FormsModule in your module or standalone component's imports array to use ngModel.

Examples

Binds the input value to the username property in your component. Typing updates username, and changing username updates the input.

Angular

<input [(ngModel)]="username" />

Two-way binds a textarea to the description property.

Angular

<textarea [(ngModel)]="description"></textarea>

Two-way binds a dropdown select to selectedOption.

Angular

<select [(ngModel)]="selectedOption">
  <option value="1">One</option>
  <option value="2">Two</option>
</select>

Sample Program

This component shows a text input bound to the name property. When you type your name, the greeting updates instantly below.

Angular

import { Component } from '@angular/core';
import { FormsModule } from '@angular/forms';

@Component({
  selector: 'app-two-way-binding',
  standalone: true,
  imports: [FormsModule],
  template: `
    <label for="nameInput">Name:</label>
    <input id="nameInput" [(ngModel)]="name" aria-label="Name input" />
    <p>Hello, {{ name }}!</p>
  `
})
export class TwoWayBindingComponent {
  name = '';
}

Important Notes

Always import FormsModule in your module or standalone component's imports array to use ngModel.

Use aria-label or label elements for accessibility.

Two-way binding is great for simple forms but consider reactive forms for complex validation.

Summary

Two-way binding keeps form inputs and component data in sync automatically.

Use [(ngModel)] to bind input elements to component properties.

Remember to import FormsModule and add accessibility labels.

Practice

1. What does the [(ngModel)] directive do in Angular forms?

easy

A. It creates a two-way binding between the input field and the component property.

B. It only updates the component property when the form is submitted.

C. It binds the input field to a CSS class dynamically.

D. It disables the input field until a condition is met.

Solution

1. Step 1: Understand the purpose of [(ngModel)]

   This directive links the input element's value and the component's property so changes in one reflect in the other automatically.

2. Step 2: Compare options with this behavior

   Only "It creates a two-way binding between the input field and the component property." describes this two-way binding behavior correctly; others describe unrelated or incorrect behaviors.

3. Final Answer:

   It creates a two-way binding between the input field and the component property. -> Option A

4. Quick Check:

   Two-way binding = [(ngModel)] [OK]

Hint: Remember: [(ngModel)] syncs input and data both ways [OK]

Common Mistakes:

• Thinking [(ngModel)] only updates on submit
• Confusing ngModel with CSS binding
• Assuming it disables inputs

2. Which of the following is the correct syntax to bind an input's value to a component property username using two-way binding?

easy

A.

B.

C.

D.

Solution

1. Step 1: Recall Angular two-way binding syntax

   Two-way binding uses the banana-in-a-box syntax: [(ngModel)] to bind and listen simultaneously.

2. Step 2: Match syntax with options

   Only <input [(ngModel)]="username"> uses [(ngModel)] correctly; others use one-way binding or invalid syntax.

3. Final Answer:

   <input [(ngModel)]="username"> -> Option D

4. Quick Check:

   Two-way binding syntax = [(ngModel)] [OK]

Hint: Use banana brackets [( )] around ngModel for two-way binding [OK]

Common Mistakes:

• Using only square brackets or parentheses alone
• Forgetting the quotes around the property
• Using plain ngModel without brackets

3. Given this component code:

export class MyComponent {
  name = 'Alice';
}

And this template snippet:

<input [(ngModel)]="name">
<p>Hello, {{ name }}!</p>

What will be displayed if the user types "Bob" in the input field?

medium

A. Hello, Alice!

B. Hello, !

C. Hello, Bob!

D. Hello, {{ name }}!

Solution

1. Step 1: Understand two-way binding effect on component property

   Typing "Bob" updates the name property in the component because of [(ngModel)].

2. Step 2: Check template interpolation

   The paragraph uses {{ name }}, so it reflects the updated value "Bob" immediately.

3. Final Answer:

   Hello, Bob! -> Option C

4. Quick Check:

   Input changes update property and view [OK]

Hint: Two-way binding updates both input and displayed text instantly [OK]

Common Mistakes:

• Thinking interpolation won't update after input change
• Confusing interpolation syntax with literal text
• Ignoring two-way binding effect

4. What is the main issue with this Angular template snippet?

<input [(ngModel)]="email">

Assuming the component has a property email defined, but the app throws an error at runtime.

medium

A. Missing import of FormsModule in the module.

B. The property email is not initialized in the component.

C. The input element is missing a closing tag.

D. Two-way binding syntax is incorrect; should use [ngModel].

Solution

1. Step 1: Identify common runtime error cause for ngModel

   Using [(ngModel)] requires importing FormsModule in the Angular module; missing it causes errors.

2. Step 2: Evaluate other options

   Property initialization is optional; input tags can be self-closing; syntax is correct with [(ngModel)].

3. Final Answer:

   Missing import of FormsModule in the module. -> Option A

4. Quick Check:

   FormsModule import required for ngModel [OK]

Hint: Always import FormsModule to use ngModel [OK]

Common Mistakes:

• Forgetting to import FormsModule
• Assuming property must be initialized
• Confusing input tag syntax
• Misreading two-way binding syntax

5. You want to create a form with two inputs: firstName and lastName, both using two-way binding. You also want to display the full name dynamically as "First Last". Which template code correctly implements this with accessibility in mind?

hard

A.

Hello, {{ firstName + ' ' + lastName }}!

B. First Name

Last Name

Hello, {{ firstName }} {{ lastName }}!

C. First Name
Last Name
Hello, {{ firstName + ' ' + lastName }}!

D.

Hello, {{ firstName }} {{ lastName }}!

Solution

1. Step 1: Check for proper labels and accessibility

   <label for="first">First Name</label> <input id="first" [(ngModel)]="firstName" aria-label="First Name"> <label for="last">Last Name</label> <input id="last" [(ngModel)]="lastName" aria-label="Last Name"> <p>Hello, {{ firstName }} {{ lastName }}!</p> uses <label for=...> with matching id on inputs and includes aria-label, improving accessibility.

2. Step 2: Verify two-way binding and display

   Both inputs use [(ngModel)] correctly, and the full name is displayed with interpolation combining both properties.

3. Final Answer:

   <label for="first">First Name</label> <input id="first" [(ngModel)]="firstName" aria-label="First Name"> <label for="last">Last Name</label> <input id="last" [(ngModel)]="lastName" aria-label="Last Name"> <p>Hello, {{ firstName }} {{ lastName }}!</p> -> Option B

4. Quick Check:

   Labels with for/id + ngModel + interpolation = <label for="first">First Name</label> <input id="first" [(ngModel)]="firstName" aria-label="First Name"> <label for="last">Last Name</label> <input id="last" [(ngModel)]="lastName" aria-label="Last Name"> <p>Hello, {{ firstName }} {{ lastName }}!</p> [OK]

Hint: Use with matching input id for accessibility [OK]

Common Mistakes:

• Omitting labels or using labels without for/id
• Not combining names properly in display
• Missing aria-labels for screen readers