Reactive forms vs template forms decision in Angular - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the module needed for reactive forms in Angular.

Angular

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

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

ARouterModule

BHttpClientModule

CReactiveFormsModule

DFormsModule

Attempts:

3 left

💡 Hint

Common Mistakes

Importing FormsModule instead of ReactiveFormsModule

Importing unrelated modules like HttpClientModule

The ReactiveFormsModule is required to use reactive forms in Angular.

2fill in blank

medium

Complete the code to create a form control in a reactive form.

Angular

this.myForm = new FormGroup({ name: new [1]('') });

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

AFormControl

BFormBuilder

CFormArray

DFormGroup

Attempts:

3 left

💡 Hint

Common Mistakes

Using FormGroup instead of FormControl for a single input

Using FormBuilder directly in this place

FormControl creates a single control in a reactive form.

3fill in blank

hard

Fix the error in the template to bind a reactive form control named 'email'.

Angular

<input type="email" [1]="myForm.get('email')">

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

A[(ngModel)]

B[formControl]

CformControlName

DngModel

Attempts:

3 left

💡 Hint

Common Mistakes

Using ngModel which is for template-driven forms

Using formControlName without a parent FormGroup directive

Use [formControl] to bind a FormControl instance in reactive forms.

4fill in blank

hard

Fill both blanks to create a template-driven form input with two-way binding.

Angular

<input type="text" name="username" [1]="username" [2]>

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

A[(ngModel)]

BformControl

Crequired

DformControlName

Attempts:

3 left

💡 Hint

Common Mistakes

Using formControl or formControlName in template-driven forms

Forgetting to add the required attribute for validation

Template-driven forms use [(ngModel)] for two-way binding and required for validation.

5fill in blank

hard

Fill the blank to define a reactive form with a FormBuilder and add a required validator.

Angular

this.myForm = this.fb.group({ email: ['', [1].required] });

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

AValidators

BFormControl

CFormGroup

DFormBuilder

Attempts:

3 left

💡 Hint

Common Mistakes

Using FormControl or FormGroup instead of Validators for validation

Confusing FormBuilder with Validators

The Validators class provides built-in validators like required for reactive forms.

Practice

1. Which form approach in Angular is best suited for simple forms managed mostly in HTML?

easy

A. Reactive forms

B. Both are equally complex

C. Template-driven forms

D. Neither, Angular does not support forms

Solution

1. Step 1: Understand form complexity

   Simple forms with minimal logic are easier to manage directly in HTML templates.

2. Step 2: Match form type to complexity

   Template-driven forms are designed for this use case, relying on Angular directives in HTML.

3. Final Answer:

   Template-driven forms -> Option C

4. Quick Check:

   Simple forms = Template-driven forms [OK]

Hint: Simple HTML forms use template-driven approach [OK]

Common Mistakes:

• Confusing reactive forms as simpler
• Thinking both are equally suited for simple forms
• Believing Angular doesn't support template forms

2. Which syntax correctly initializes a reactive form in Angular's TypeScript component?

easy

A. this.form = new FormGroup({ name: new FormControl('') });

B. this.form = new NgForm({ name: '' });

C. this.form = new TemplateForm({ name: '' });

D. this.form = new FormBuilder({ name: '' });

Solution

1. Step 1: Recall reactive form initialization

   Reactive forms use FormGroup and FormControl classes to define form structure in TypeScript.

2. Step 2: Identify correct syntax

   this.form = new FormGroup({ name: new FormControl('') }); correctly creates a FormGroup with a FormControl named 'name'.

3. Final Answer:

   this.form = new FormGroup({ name: new FormControl('') }); -> Option A

4. Quick Check:

   Reactive form init uses FormGroup and FormControl [OK]

Hint: Reactive forms use FormGroup and FormControl classes [OK]

Common Mistakes:

• Using NgForm which is for template forms
• Confusing FormBuilder usage without calling group()
• Trying to initialize reactive forms like template forms

3. Given this reactive form code snippet, what will be the output of console.log(this.form.value) after setting this.form.controls['email'].setValue('[e-mail]')?

this.form = new FormGroup({ email: new FormControl('') });

medium

A. { email: '[e-mail]' }

B. { email: '' }

C. undefined

D. Error: controls is not defined

Solution

1. Step 1: Understand form initialization

   The form is initialized with an 'email' control starting as an empty string.

2. Step 2: Setting control value

   Calling setValue on 'email' updates its value to '[e-mail]'.

3. Step 3: Checking form value output

   Logging form.value returns an object with the current control values, so it shows the updated email.

4. Final Answer:

   { email: '[e-mail]' } -> Option A

5. Quick Check:

   Reactive form values reflect control updates [OK]

Hint: FormGroup.value shows current control values [OK]

Common Mistakes:

• Expecting empty string after setValue call
• Confusing controls property access
• Assuming form.value is undefined before submit

4. Identify the error in this template-driven form snippet:

<form #myForm="ngForm">
  <input name="username" ngModel>
  <button type="submit">Submit</button>
</form>

medium

A. Missing 'name' attribute on input element

B. No error, the form is correct

C. Missing 'ngModel' directive on input element

D. Form tag missing 'ngForm' directive

Solution

1. Step 1: Check input element attributes

   The input has both 'name' and 'ngModel' directives, which are required for template-driven forms.

2. Step 2: Check form tag

   The form uses '#myForm="ngForm"' which correctly references the Angular form directive.

3. Final Answer:

   No error, the form is correct -> Option B

4. Quick Check:

   Template form with name and ngModel is valid [OK]

Hint: Template forms need name and ngModel on inputs [OK]

Common Mistakes:

• Forgetting name attribute on inputs
• Confusing ngForm with reactive form syntax
• Assuming form tag needs extra directives

5. You need to build a complex form with dynamic validation and conditional fields in Angular. Which form approach should you choose and why?

hard

A. Use plain HTML forms without Angular features

B. Template-driven forms, because they are simpler to write in HTML

C. Either approach works equally well for complex dynamic forms

D. Reactive forms, because they allow better control and dynamic logic in TypeScript

Solution

1. Step 1: Analyze form complexity and requirements

   Complex forms with dynamic validation and conditional fields require programmatic control.

2. Step 2: Match form approach to needs

   Reactive forms provide APIs in TypeScript to add/remove controls and validations dynamically.

3. Step 3: Compare with template-driven forms

   Template-driven forms are less suited for complex logic as they rely mostly on HTML directives.

4. Final Answer:

   Reactive forms, because they allow better control and dynamic logic in TypeScript -> Option D

5. Quick Check:

   Complex dynamic forms = Reactive forms [OK]

Hint: Use reactive forms for complex, dynamic form logic [OK]

Common Mistakes:

• Choosing template forms for complex dynamic needs
• Assuming both approaches handle dynamic validation equally
• Ignoring benefits of TypeScript control in reactive forms