ngOnInit for initialization in Angular - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is ngOnInit in Angular?

ngOnInit is a lifecycle hook method in Angular components. It runs once after the component's data-bound properties are initialized. It is used to perform component initialization tasks.

beginner

When is ngOnInit called in the component lifecycle?

ngOnInit is called shortly after the component is created and after Angular sets the input properties. It happens before the component is displayed.

intermediate

Why should you use ngOnInit instead of the constructor for initialization?

The constructor is for simple setup like dependency injection. ngOnInit is better for initialization that needs Angular bindings or inputs to be ready.

beginner

How do you implement ngOnInit in an Angular component?

Implement the OnInit interface and add the ngOnInit() method inside your component class. Angular calls this method automatically.

intermediate

Can ngOnInit be async? How to handle async initialization?

Yes, ngOnInit can be async by marking it async. You can use await inside it to wait for data before continuing.

What is the main purpose of ngOnInit in Angular?

A To handle user events

B To initialize component data after inputs are set

C To define component styles

D To create services

ngOnInit is used to initialize component data after Angular sets input properties.

When is ngOnInit called during the component lifecycle?

A After input properties are set but before display

B After the component is displayed

C Before the constructor

D Only when the component is destroyed

ngOnInit runs after inputs are set but before the component is shown.

Which interface must a component implement to use ngOnInit?

A OnInit

B AfterViewInit

C OnDestroy

D DoCheck

The OnInit interface defines the ngOnInit method.

Why is it better to put initialization code in ngOnInit rather than the constructor?

A Because <code>ngOnInit</code> is optional

B Because <code>ngOnInit</code> runs multiple times

C Because constructors cannot access inputs

D Because constructors are slower

Inputs are not yet set in the constructor, so initialization depending on inputs should be in ngOnInit.

Can ngOnInit be asynchronous to wait for data?

A Only in AngularJS

B No, it must be synchronous

C Only if you use Observables

D Yes, by marking it <code>async</code> and using <code>await</code>

You can mark ngOnInit as async and use await inside it to handle async tasks.

Explain what ngOnInit is and why it is important for Angular component initialization.

Think about when Angular sets input properties and when you want to run your setup code.

Describe how to implement ngOnInit in a component and how to handle asynchronous initialization inside it.

Remember the syntax and how async/await works in modern JavaScript/TypeScript.

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