FormsModule setup in Angular - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when FormsModule is not imported?

Consider an Angular component template using [(ngModel)] for two-way binding on an input field. What will happen if the FormsModule is not imported in the module?

Angular

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

A The input field binds correctly but changes are not reflected in the component.

B The input field works normally without any errors or warnings.

C The application throws a template parse error about unknown directive 'ngModel'.

D The application compiles but the input field is disabled automatically.

💡 Hint

Think about what Angular needs to recognize ngModel in templates.

Without importing FormsModule, Angular does not know about the ngModel directive. This causes a template parse error.

📝 Syntax

intermediate

Correct way to import FormsModule in Angular standalone component

You have a standalone Angular component that uses [(ngModel)]. Which is the correct way to import FormsModule for this component?

Angular

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

@Component({
  selector: 'app-input',
  standalone: true,
  imports: [/* What goes here? */],
  template: `<input [(ngModel)]="name" />`
})
export class InputComponent {
  name = '';
}

A imports: [FormsModule]

B imports: []

C imports: [CommonModule]

D imports: [BrowserModule]

💡 Hint

Which module provides the ngModel directive?

For standalone components, you must explicitly import FormsModule in the imports array to use ngModel.

❓ state_output

advanced

What is the value of the model after input change?

Given this Angular component using FormsModule, what will be the value of userName after the user types 'Angular' in the input field?

Angular

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

@Component({
  selector: 'app-user',
  template: `<input [(ngModel)]="userName" />`,
  standalone: true,
  imports: [FormsModule]
})
export class UserComponent {
  userName = '';
}

A undefined

B "Angular"

C "" (empty string)

D null

💡 Hint

Two-way binding updates the property as the input changes.

The [(ngModel)] directive binds the input value to the userName property. Typing 'Angular' updates userName to 'Angular'.

🔧 Debug

advanced

Why does this form control not update the model?

This Angular component uses FormsModule and ngModel, but the model property does not update when typing. What is the likely cause?

Angular

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

@Component({
  selector: 'app-debug',
  template: `<input [ngModel]="email" />`,
  standalone: true,
  imports: [FormsModule]
})
export class DebugComponent {
  email = '';
}

A Missing two-way binding syntax; should use [(ngModel)] instead of [ngModel].

B The input element is missing a name attribute, so ngModel fails.

C The email property is not initialized, causing binding failure.

D FormsModule is not imported, so ngModel does not work.

💡 Hint

Check the difference between one-way and two-way binding syntax.

Using [ngModel] binds the input value one-way only. To update the model on input changes, use [(ngModel)] for two-way binding.

🧠 Conceptual

expert

Why is FormsModule needed for template-driven forms?

Which statement best explains why Angular requires importing FormsModule to use template-driven forms with ngModel?

A FormsModule registers global event listeners for all form inputs to detect changes.

B FormsModule provides CSS styles that make form controls visually consistent across browsers.

C FormsModule automatically imports ReactiveFormsModule to enable reactive form features.

D FormsModule declares and exports the <code>ngModel</code> directive and related providers needed for two-way binding and validation.

💡 Hint

Think about what Angular needs to recognize and process ngModel in templates.

FormsModule contains the ngModel directive and the services Angular uses to support template-driven forms, including two-way binding and validation.