Two-way binding in forms in Angular - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to bind the input value to the component property using two-way binding.

Angular

<input type="text" [(ngModel)]="[1]">

Drag options to blanks, or click blank then click option'

Ausername

BuserName

Cuser_name

Duser

Attempts:

3 left

💡 Hint

Common Mistakes

Using one-way binding syntax like [ngModel] instead of [(ngModel)]

Misspelling the property name

The [(ngModel)] directive binds the input value to the username property in the component, enabling two-way binding.

2fill in blank

medium

Complete the code to import the module needed for two-way binding in Angular forms.

Angular

import { [1] } from '@angular/forms';

Drag options to blanks, or click blank then click option'

AReactiveFormsModule

BFormsModule

CHttpClientModule

DBrowserModule

Attempts:

3 left

💡 Hint

Common Mistakes

Importing ReactiveFormsModule instead of FormsModule

Forgetting to import any forms module

The FormsModule must be imported to use [(ngModel)] for two-way binding in template-driven forms.

3fill in blank

hard

Fix the error in the component template to correctly bind the input value two-way.

Angular

<input type="text" [1]>

Drag options to blanks, or click blank then click option'

AuserName

B[(ngModel)]="userName"

C[(ngModel)]="username"

Dusername

Attempts:

3 left

💡 Hint

Common Mistakes

Using only [ngModel] without parentheses

Using curly braces inside the attribute

Two-way binding requires the syntax [(ngModel)]="propertyName". Using only [ngModel] is one-way binding.

4fill in blank

hard

Fill both blanks to complete the component decorator for enabling two-way binding.

Angular

@Component({
  selector: 'app-user',
  templateUrl: './user.component.html',
  imports: [[1]],
  standalone: [2]
})

Drag options to blanks, or click blank then click option'

AFormsModule

BHttpClientModule

Ctrue

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Setting standalone to false

Importing wrong modules

To use two-way binding in a standalone component, import FormsModule and set standalone to true.

5fill in blank

hard

Fill all three blanks to create a two-way bound input with a label and bind it to the 'email' property.

Angular

<label for="emailInput">Email:</label>
<input id="emailInput" type="email" [1]="email" [2] [3]>

Drag options to blanks, or click blank then click option'

Aname

B[(ngModel)]="email"

Crequired

Dplaceholder

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting the name attribute

Using [ngModel] instead of [(ngModel)]

Forgetting required attribute

The input needs a name attribute for forms, [(ngModel)]="email" for two-way binding, and required for validation.

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