ngOnInit for initialization in Angular - Step-by-Step Execution

Concept Flow - ngOnInit for initialization

Component Created

↓

Constructor Runs

↓

ngOnInit Called

↓

Initialize Data

↓

Component Ready to Render

Angular calls ngOnInit after the component is created and constructor runs, to initialize data before rendering.

Execution Sample

Angular

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

@Component({ selector: 'app-sample', template: '{{message}}' })
export class SampleComponent implements OnInit {
  message = '';
  ngOnInit() {
    this.message = 'Hello from ngOnInit!';
  }
}

This component sets a message string inside ngOnInit, which updates the displayed text after initialization.

Execution Table

Step	Action	State Before	State After	Rendered Output
1	Component instance created	message = ''	message = ''
2	Constructor runs	message = ''	message = ''
3	ngOnInit called	message = ''	message = 'Hello from ngOnInit!'
4	Angular renders template	message = 'Hello from ngOnInit!'	message = 'Hello from ngOnInit!'	Hello from ngOnInit!

💡 ngOnInit completes, component data initialized, template rendered with updated message.

Variable Tracker

Variable	Start	After ngOnInit	Final
message	'' (empty string)	'Hello from ngOnInit!'	'Hello from ngOnInit!'

Key Moments - 2 Insights

Why is ngOnInit used instead of the constructor for initialization?

ngOnInit runs after Angular sets up input properties and component is ready, so initialization depending on inputs or Angular features should be done here, not in the constructor (see execution_table step 3).

What happens if you update variables before ngOnInit?

Variables set in the constructor exist but Angular may not have set inputs yet, so initialization depending on inputs might be incorrect. ngOnInit ensures Angular setup is done (see execution_table steps 1-3).

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'message' right after the constructor runs?

A '' (empty string)

B 'Hello from ngOnInit!'

C undefined

D null

💡 Hint

Check the 'State After' column at step 2 in the execution_table.

At which step does the component's displayed message update to 'Hello from ngOnInit!'?

A Step 1

B Step 3

C Step 4

D Step 2

💡 Hint

Look at the 'Rendered Output' column in the execution_table.

If you set 'message' in the constructor instead of ngOnInit, what might happen?

A Message initializes correctly before rendering.

B Message might initialize too early, before Angular sets inputs.

C Component will not render at all.

D ngOnInit will not be called.

💡 Hint

Refer to key_moments about constructor vs ngOnInit timing.

Concept Snapshot

ngOnInit is a lifecycle hook Angular calls after component creation and input setup.
Use ngOnInit to initialize data or fetch info needed before rendering.
Constructor runs earlier but should not depend on Angular inputs.
ngOnInit ensures component is ready for initialization.
Syntax: implement OnInit interface and define ngOnInit() method.

Full Transcript

In Angular, the ngOnInit method runs after the component is created and Angular sets up input properties. First, the component instance is created with default values. Then the constructor runs but should not contain complex initialization depending on Angular features. Next, ngOnInit is called where you can safely initialize variables or fetch data. Finally, Angular renders the template using the initialized data. This sequence ensures your component is ready and data is set before display.

Practice

1. What is the main purpose of the ngOnInit method in an Angular component?

easy

A. To run initialization code after the component is created

B. To handle user input events

C. To define the component's HTML template

D. To style the component with CSS

Solution

1. Step 1: Understand the role of ngOnInit

   The ngOnInit lifecycle hook runs after Angular creates the component, making it ideal for initialization tasks.

2. Step 2: Differentiate from other component parts

   Handling user input, defining templates, and styling are done elsewhere, not in ngOnInit.

3. Final Answer:

   To run initialization code after the component is created -> Option A

4. Quick Check:

   ngOnInit = initialization after creation [OK]

Hint: ngOnInit runs once after component setup [OK]

Common Mistakes:

• Confusing ngOnInit with event handlers
• Thinking ngOnInit sets styles or templates
• Using ngOnInit for user input processing

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

easy

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

B. ngOnInit: function() { console.log('Init'); }

C. function ngOnInit() { console.log('Init'); }

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

Solution

1. Step 1: Recall Angular lifecycle hook syntax

   In Angular components, lifecycle hooks like ngOnInit are methods declared as ngOnInit() { ... }.

2. Step 2: Identify incorrect syntax

   The other options use invalid syntax in an Angular class: shorthand property with function, standalone function declaration, and wrong method name.

3. Final Answer:

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

4. Quick Check:

   ngOnInit is a method, not a property or function keyword [OK]

Hint: Use method syntax: ngOnInit() { } [OK]

Common Mistakes:

• Using function keyword inside class
• Naming method incorrectly as onInit
• Using colon instead of parentheses

3. Consider this Angular component code snippet:

export class MyComponent implements OnInit {
  data = '';
  ngOnInit() {
    this.data = 'Hello World';
  }
}

What will be the value of data after the component initializes?

medium

A. '' (empty string)

B. undefined

C. null

D. 'Hello World'

Solution

1. Step 1: Check initial value of data

   The property data starts as an empty string.

2. Step 2: See what ngOnInit does

   Inside ngOnInit, data is set to 'Hello World'. This runs after component creation.

3. Final Answer:

   'Hello World' -> Option D

4. Quick Check:

   ngOnInit sets data to 'Hello World' [OK]

Hint: ngOnInit runs after creation, sets data [OK]

Common Mistakes:

• Assuming data stays empty string
• Confusing initialization timing
• Thinking ngOnInit runs before constructor

4. Identify the error in this Angular component code:

export class SampleComponent implements OnInit {
  message: string;
  ngOnInit() {
    this.message = 'Welcome';
  }
}

medium

A. ngOnInit method name is incorrect

B. message property should be initialized in constructor

C. Missing import of OnInit interface

D. No error, code is correct

Solution

1. Step 1: Check for required imports

   The component implements OnInit but does not import it from '@angular/core'. This causes a compile error.

2. Step 2: Verify method and property usage

   The method name ngOnInit is correct, and initializing message in ngOnInit is valid.

3. Final Answer:

   Missing import of OnInit interface -> Option C

4. Quick Check:

   Implementing OnInit requires importing it [OK]

Hint: Always import lifecycle interfaces from '@angular/core' [OK]

Common Mistakes:

• Forgetting to import OnInit
• Renaming ngOnInit incorrectly
• Thinking properties must initialize in constructor

5. You want to fetch user data from a server right after your Angular component is created. Where should you place the fetch call to ensure it runs once after initialization?

hard

A. Inside the constructor

B. Inside the ngOnInit method

C. Inside the ngOnDestroy method

D. Inside a button click event handler

Solution

1. Step 1: Understand lifecycle timing

   The constructor runs before Angular sets up the component fully, so it's not ideal for async tasks like fetching data.

2. Step 2: Use ngOnInit for initialization tasks

   ngOnInit runs after component creation and is the recommended place to start fetching data once.

3. Step 3: Exclude other options

   ngOnDestroy runs when component is destroyed, and button click handlers run on user action, not automatically.

4. Final Answer:

   Inside the ngOnInit method -> Option B

5. Quick Check:

   Fetch data in ngOnInit for one-time setup [OK]

Hint: Fetch data in ngOnInit, not constructor [OK]

Common Mistakes:

• Fetching data in constructor causing timing issues
• Using ngOnDestroy which runs too late
• Waiting for user click instead of auto-fetch