Why reactive forms are preferred in Angular - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

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

Angular

const nameControl = new FormControl([1]);

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

A0

Bnull

C''

Dundefined

Attempts:

3 left

💡 Hint

Common Mistakes

Null or undefined are valid initial values but an empty string is preferred for text inputs.

Using 0 is not suitable for text inputs.

Reactive forms use FormControl to create form controls with initial values. An empty string '' is a common initial value for text inputs.

2fill in blank

medium

Complete the code to add a required validator to a reactive form control.

Angular

const emailControl = new FormControl('', [1]);

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

AValidators.pattern('[a-z]+')

BValidators.required

CValidators.maxLength(10)

DValidators.minLength(5)

Attempts:

3 left

💡 Hint

Common Mistakes

Using minLength or maxLength does not enforce a value is present.

Pattern validator checks format but not presence.

The Validators.required ensures the form control must have a value before the form is valid.

3fill in blank

hard

Fix the error in the reactive form group declaration.

Angular

this.form = new FormGroup({
  username: new FormControl('', [1])
});

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

AValidators.email

BValidators.max(10)

CValidators.min(5)

DValidators.required

Attempts:

3 left

💡 Hint

Common Mistakes

Using Validators.email for username is incorrect.

Min and max validators are for numbers, not strings.

Adding Validators.required ensures the username field cannot be empty, which is a common requirement.

4fill in blank

hard

Fill both blanks to create a reactive form group with two controls and validators.

Angular

this.loginForm = new FormGroup({
  email: new FormControl('', [1]),
  password: new FormControl('', [2])
});

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

AValidators.required

BValidators.minLength(6)

CValidators.email

DValidators.maxLength(10)

Attempts:

3 left

💡 Hint

Common Mistakes

Using required only without format or length checks.

Mixing up minLength and maxLength.

The email control needs Validators.email to check format, and the password control needs Validators.minLength(6) to ensure a minimum length.

5fill in blank

hard

Fill all three blanks to create a reactive form with controls, validators, and a submit handler.

Angular

this.profileForm = new FormGroup({
  firstName: new FormControl('', [1]),
  age: new FormControl('', [2]),
  email: new FormControl('', [3])
});

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

AValidators.required

BValidators.min(18)

CValidators.email

DValidators.maxLength(20)

Attempts:

3 left

💡 Hint

Common Mistakes

Not using required validator for first name.

Using maxLength instead of min for age.

Missing email format validation.

First name is required, age must be at least 18, and email must be valid format.

Practice

1. Why are reactive forms preferred in Angular over template-driven forms?

easy

A. They provide better control and scalability for complex forms.

B. They require less code and are simpler for small forms.

C. They automatically generate UI without coding.

D. They do not support validation.

Solution

1. Step 1: Understand form control in Angular

   Reactive forms allow explicit creation and management of form controls in the component class, giving better control.

2. Step 2: Compare with template-driven forms

   Template-driven forms are simpler but less scalable and harder to manage for complex forms.

3. Final Answer:

   They provide better control and scalability for complex forms. -> Option A

4. Quick Check:

   Reactive forms = better control and scalability [OK]

Hint: Reactive forms = explicit control, best for complex forms [OK]

Common Mistakes:

• Thinking reactive forms are simpler for small forms
• Believing reactive forms auto-generate UI
• Assuming reactive forms lack validation

2. Which of the following is the correct way to create a reactive form control in Angular?

easy

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

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

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

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

Solution

1. Step 1: Recall Angular reactive form syntax

   The correct class to create a group of controls is FormGroup, and individual controls use FormControl.

2. Step 2: Check the options for correct class names

   Only this.form = new FormGroup({ name: new FormControl('') }); uses the correct Angular classes: FormGroup and FormControl.

3. Final Answer:

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

4. Quick Check:

   FormGroup + FormControl = correct syntax [OK]

Hint: FormGroup holds controls; FormControl defines each input [OK]

Common Mistakes:

• Using incorrect class names like FormControlGroup
• Mixing up FormGroup and ControlGroup
• Omitting new keyword

3. Given this reactive form code snippet, what will be the output when console.log(this.form.value) is called after initialization?

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

medium

A. { email: '', password: '1234' }

B. { email: null, password: null }

C. { email: undefined, password: '1234' }

D. Error: form not initialized

Solution

1. Step 1: Check initial values of form controls

   The email control is initialized with an empty string '', and password with '1234'.

2. Step 2: Understand form.value output

   Calling form.value returns an object with current values of each control.

3. Final Answer:

   { email: '', password: '1234' } -> Option A

4. Quick Check:

   form.value = current control values [OK]

Hint: form.value shows current control values as object [OK]

Common Mistakes:

• Assuming uninitialized controls are null or undefined
• Expecting error without initialization
• Confusing form.value with form.controls

4. Identify the error in this reactive form setup:

this.form = new FormGroup({
  username: FormControl('user1'),
  age: new FormControl(25)
});

medium

A. FormGroup should be FormControlGroup.

B. FormGroup cannot have more than one control.

C. Age control value must be a string, not a number.

D. FormControl is missing the 'new' keyword for username control.

Solution

1. Step 1: Check syntax for creating FormControl

   FormControl must be instantiated with 'new' keyword to create a control instance.

2. Step 2: Identify the incorrect usage

   Username control uses FormControl('user1') without 'new', causing a syntax/runtime error.

3. Final Answer:

   FormControl is missing the 'new' keyword for username control. -> Option D

4. Quick Check:

   Always use 'new FormControl()' to create controls [OK]

Hint: Remember: 'new' keyword is required for FormControl [OK]

Common Mistakes:

• Omitting 'new' before FormControl
• Using wrong class names like FormControlGroup
• Thinking numeric values are invalid for controls

5. You want to build a dynamic form where fields can be added or removed at runtime. Why is using reactive forms preferred in this case?

hard

A. Reactive forms do not support dynamic changes once initialized.

B. Template-driven forms automatically handle dynamic fields without code.

C. Reactive forms allow programmatic control to add or remove controls easily.

D. Template-driven forms provide better validation for dynamic fields.

Solution

1. Step 1: Understand dynamic form requirements

   Dynamic forms need adding/removing controls during runtime based on user actions.

2. Step 2: Compare reactive and template-driven forms

   Reactive forms provide APIs like addControl and removeControl for easy dynamic updates, while template-driven forms lack this flexibility.

3. Final Answer:

   Reactive forms allow programmatic control to add or remove controls easily. -> Option C

4. Quick Check:

   Dynamic forms = reactive forms for control [OK]

Hint: Use reactive forms for dynamic field control [OK]

Common Mistakes:

• Assuming template-driven forms handle dynamic fields automatically
• Believing reactive forms are static after creation
• Confusing validation capabilities between form types