Why lifecycle hooks matter in Angular - See It in Action

Why lifecycle hooks matter

📖 Scenario: You are building a simple Angular component that shows a message and tracks how many times it has been initialized. This helps understand how Angular lifecycle hooks work in real apps.

🎯 Goal: Create an Angular standalone component that uses the OnInit lifecycle hook to count how many times the component has been initialized and display this count in the template.

📋 What You'll Learn

Create a standalone Angular component named InitCounterComponent

Add a property initCount initialized to 0

Implement the OnInit interface and its ngOnInit() method

Increment initCount inside ngOnInit()

Display the text Component initialized X times in the template, where X is initCount

💡 Why This Matters

🌍 Real World

Understanding lifecycle hooks helps developers manage component setup and cleanup in real Angular apps, improving performance and user experience.

💼 Career

Knowing lifecycle hooks is essential for Angular developers to write maintainable, efficient components that behave correctly during their lifecycle.

1

Create the component with initial count

Create a standalone Angular component named InitCounterComponent with a property initCount set to 0. Use the @Component decorator with selector set to 'app-init-counter' and a simple template showing initCount inside a <p> tag.

Angular

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

@Component({
  selector: 'app-init-counter',
  standalone: true,
  template: `Initialized 0 times`
})
export class InitCounterComponent {
  // Your code here
}

Hint

Use @Component with standalone: true and define initCount as a number property set to 0.

2

Add OnInit interface and import

Import OnInit from @angular/core and make InitCounterComponent implement OnInit. Add the ngOnInit() method with an empty body.

Angular

import { Component, OnInit } from '@angular/core';

@Component({
  selector: 'app-init-counter',
  standalone: true,
  template: `Initialized {{ initCount }} times`
})
export class InitCounterComponent implements OnInit {
  initCount = 0;

  // Your code here
}

Hint

Remember to import OnInit and add implements OnInit after the class name.

3

Increment count inside ngOnInit

Inside the ngOnInit() method, increment the initCount property by 1 using this.initCount++.

Angular

import { Component, OnInit } from '@angular/core';

@Component({
  selector: 'app-init-counter',
  standalone: true,
  template: `Initialized {{ initCount }} times`
})
export class InitCounterComponent implements OnInit {
  initCount = 0;

  ngOnInit() {
    // Your code here
  }
}

Hint

Use this.initCount++ inside ngOnInit() to increase the count.

4

Complete template to show initialization count

Ensure the component template displays the text Component initialized X times where X is the value of initCount. Update the template property in the @Component decorator accordingly.

Angular

import { Component, OnInit } from '@angular/core';

@Component({
  selector: 'app-init-counter',
  standalone: true,
  // Your code here
})
export class InitCounterComponent implements OnInit {
  initCount = 0;

  ngOnInit() {
    this.initCount++;
  }
}

Hint

Update the template string to exactly show Component initialized {{ initCount }} times.

Practice

1. Why are lifecycle hooks important in Angular components?

easy

A. They make components load faster by default.

B. They automatically style your components.

C. They replace the need for services.

D. They let you run code at specific times during a component's life.

Solution

1. Step 1: Understand what lifecycle hooks do

   Lifecycle hooks allow you to run code at key moments like creation, update, or destruction of a component.

2. Step 2: Identify the main benefit

   This helps manage resources and keep the app efficient by running code only when needed.

3. Final Answer:

   They let you run code at specific times during a component's life. -> Option D

4. Quick Check:

   Lifecycle hooks = run code at key moments [OK]

Hint: Lifecycle hooks run code at key moments [OK]

Common Mistakes:

• Thinking lifecycle hooks style components
• Believing hooks replace services
• Assuming hooks speed up loading automatically

2. Which of the following is the correct syntax to implement the ngOnInit lifecycle hook in an Angular component?

easy

A. ngOnInit() { console.log('Init'); }

B. onInit() { console.log('Init'); }

C. nginit() { console.log('Init'); }

D. init() { console.log('Init'); }

Solution

1. Step 1: Recall the exact lifecycle hook name

   The correct lifecycle hook method name is ngOnInit with exact casing.

2. Step 2: Match the syntax

   The method should be declared as ngOnInit() { ... } inside the component class.

3. Final Answer:

   ngOnInit() { console.log('Init'); } -> Option A

4. Quick Check:

   Correct hook name and syntax = ngOnInit() { console.log('Init'); } [OK]

Hint: Lifecycle hooks start with 'ng' and use camelCase [OK]

Common Mistakes:

• Using wrong method names like onInit or init
• Incorrect casing like nginit
• Missing 'ng' prefix in method name

3. Given this Angular component code snippet, what will be logged to the console when the component is created?

export class MyComponent implements OnInit {
  constructor() { console.log('Constructor called'); }
  ngOnInit() { console.log('ngOnInit called'); }
}

medium

A. Constructor called\nngOnInit called

B. ngOnInit called\nConstructor called

C. Only Constructor called

D. Only ngOnInit called

Solution

1. Step 1: Understand Angular component creation order

   The constructor runs first when the component is created, then ngOnInit runs after Angular sets input properties.

2. Step 2: Trace the console logs

   First, 'Constructor called' logs, then 'ngOnInit called' logs.

3. Final Answer:

   Constructor called\nngOnInit called -> Option A

4. Quick Check:

   Constructor runs before ngOnInit [OK]

Hint: Constructor runs before ngOnInit [OK]

Common Mistakes:

• Thinking ngOnInit runs before constructor
• Expecting only one log message
• Confusing lifecycle order

4. What is wrong with this Angular component code snippet?

export class SampleComponent implements OnInit {
  ngOnInit() {
    this.loadData();
  }
  loadData() {
    console.log('Data loaded');
  }
  ngOnDestroy() {
    this.loadData();
  }
}

medium

A. ngOnInit should not be implemented without a constructor.

B. ngOnDestroy must return a value.

C. Calling loadData() inside ngOnDestroy is incorrect because it runs when component is destroyed.

D. loadData() cannot be called inside lifecycle hooks.

Solution

1. Step 1: Understand purpose of ngOnDestroy

   ngOnDestroy runs when the component is about to be removed. It is used to clean up resources, not to load data.

2. Step 2: Identify misuse of loadData()

   Calling loadData() during destruction is illogical because loading data is for initialization, not cleanup.

3. Final Answer:

   Calling loadData() inside ngOnDestroy is incorrect because it runs when component is destroyed. -> Option C

4. Quick Check:

   ngOnDestroy is for cleanup, not loading data [OK]

Hint: Use ngOnDestroy only for cleanup tasks [OK]

Common Mistakes:

• Thinking ngOnDestroy needs a return value
• Believing lifecycle hooks can't call methods
• Assuming constructor is required with ngOnInit

5. You want to fetch user data only once when a component loads and clean up a subscription when the component is destroyed. Which lifecycle hooks should you use together?

hard

A. ngOnChanges to fetch data, ngDoCheck to clean up subscription

B. ngOnInit to fetch data, ngOnDestroy to clean up subscription

C. constructor to fetch data, ngAfterViewInit to clean up subscription

D. ngAfterContentInit to fetch data, ngAfterContentChecked to clean up subscription

Solution

1. Step 1: Identify hook for initial data fetch

   Use ngOnInit to run code once after component creation, perfect for fetching data.

2. Step 2: Identify hook for cleanup

   Use ngOnDestroy to clean up resources like subscriptions before component is removed.

3. Final Answer:

   ngOnInit to fetch data, ngOnDestroy to clean up subscription -> Option B

4. Quick Check:

   Init = fetch, Destroy = cleanup [OK]

Hint: Fetch in ngOnInit, clean in ngOnDestroy [OK]

Common Mistakes:

• Using constructor for async data fetch
• Confusing ngAfterViewInit with cleanup
• Using ngOnChanges for one-time fetch