ngOnInit for initialization in Angular - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when ngOnInit runs in this Angular component?

Consider this Angular component code snippet. What will be the value of message after ngOnInit runs?

Angular

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

@Component({
  selector: 'app-welcome',
  template: `<p>{{ message }}</p>`,
  standalone: true
})
export class WelcomeComponent implements OnInit {
  message = '';

  ngOnInit() {
    this.message = 'Hello from ngOnInit!';
  }
}

A "" (empty string)

B null

C undefined

D "Hello from ngOnInit!"

💡 Hint

ngOnInit runs after the component is created but before it is displayed.

The ngOnInit method sets the message property to "Hello from ngOnInit!" before the template renders. So the displayed message will be this string.

❓ lifecycle

intermediate

When is ngOnInit called in Angular component lifecycle?

Choose the correct timing for when ngOnInit is called in an Angular component's lifecycle.

A After the component's constructor and before the first render

B Before the component's constructor runs

C After the component is destroyed

D Only when the component's inputs change

💡 Hint

Think about when initialization logic should run relative to component creation.

ngOnInit runs once after the constructor and before the component is displayed. It is the right place for initialization logic.

📝 Syntax

advanced

Identify the correct ngOnInit implementation in this Angular component

Which option correctly implements ngOnInit in this Angular component?

Angular

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

@Component({
  selector: 'app-counter',
  template: `<p>{{ count }}</p>`,
  standalone: true
})
export class CounterComponent implements OnInit {
  count = 0;

  // ngOnInit implementation goes here
}

A ngOnInit() => { this.count = 10; }

B ngOnInit() { this.count = 10; }

C function ngOnInit() { this.count = 10; }

D ngOnInit { this.count = 10; }

💡 Hint

Remember the correct method syntax inside a class in TypeScript.

Option B uses the correct method syntax for ngOnInit. Options A, B, and D have syntax errors or invalid method declarations.

🔧 Debug

advanced

Why does this ngOnInit code not update the template?

Given this Angular component, why does the template not show the updated title after ngOnInit?

Angular

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

@Component({
  selector: 'app-title',
  template: `<h1>{{ title }}</h1>`,
  standalone: true
})
export class TitleComponent implements OnInit {
  title = 'Initial';

  ngOnInit() {
    let title = 'Updated in ngOnInit';
  }
}

A The component selector is missing, so it does not render

B ngOnInit is not called automatically, so the title stays the same

C The local variable 'title' inside ngOnInit shadows the class property, so the class property is not changed

D The template binding syntax is incorrect and does not update

💡 Hint

Check variable scope inside ngOnInit.

The let title inside ngOnInit creates a new local variable that hides the class property. The class property title remains unchanged, so the template shows the initial value.

🧠 Conceptual

expert

What is the main benefit of using ngOnInit instead of constructor for initialization?

Why should you put initialization code in ngOnInit rather than the constructor in Angular components?

A ngOnInit runs after Angular sets input properties, so initialization can use them safely

B The constructor runs multiple times, but ngOnInit runs only once

C ngOnInit runs before the constructor, so it initializes earlier

D The constructor cannot access class properties, but ngOnInit can

💡 Hint

Think about when Angular sets input properties relative to constructor and ngOnInit.

The constructor runs before Angular sets input properties, so they may be undefined there. ngOnInit runs after inputs are set, so it is safe to use them for initialization.

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