ngAfterViewInit for view ready in Angular - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the ngAfterViewInit lifecycle hook in Angular?

It runs after Angular has fully initialized a component's view and its child views. It's used to perform actions that require the view to be ready, like accessing DOM elements or child components.

beginner

When exactly does ngAfterViewInit get called in the component lifecycle?

It is called once after Angular initializes the component's views and child views, right after ngAfterContentInit and before the view is displayed to the user.

intermediate

Why should you avoid manipulating the DOM directly in the constructor or ngOnInit?

Because the component's view and child views are not fully initialized yet, so DOM elements might not exist or be ready. ngAfterViewInit is the safe place for DOM access.

intermediate

How can you use ngAfterViewInit to access a child component or DOM element?

You can use Angular's @ViewChild decorator to get a reference to the child component or element, then safely interact with it inside ngAfterViewInit.

advanced

What happens if you try to update a component's data-bound property inside ngAfterViewInit without triggering change detection?

Angular may throw an error because the view has already been checked. To fix this, you can use ChangeDetectorRef.detectChanges() to update the view safely.

When is ngAfterViewInit called in Angular?

A After the component's view and child views are initialized

B Before the component's constructor runs

C Before <code>ngOnInit</code>

D After the component is destroyed

ngAfterViewInit runs after Angular initializes the component's view and child views, making it the right place to access the DOM or child components.

Which decorator is commonly used with ngAfterViewInit to access child components or elements?

A @Output

B @Input

C @ViewChild

D @Injectable

@ViewChild lets you get a reference to a child component or DOM element, which you can safely use inside ngAfterViewInit.

Why should DOM manipulation be done in ngAfterViewInit instead of ngOnInit?

A Because <code>ngOnInit</code> runs too late

B Because the view is not fully initialized in <code>ngOnInit</code>

C Because <code>ngAfterViewInit</code> runs before the constructor

D Because <code>ngOnInit</code> is only for services

The component's view and child views are not ready in ngOnInit, so DOM elements might not exist yet. ngAfterViewInit ensures the view is ready.

What might happen if you update a data-bound property inside ngAfterViewInit without triggering change detection?

A Angular throws an error about changed values after check

B Nothing happens, it's safe

C The component is destroyed

D Angular ignores the update silently

Angular may throw an error because the view was already checked. You can fix this by calling ChangeDetectorRef.detectChanges() after the update.

Which lifecycle hook runs immediately before ngAfterViewInit?

A ngOnInit

B ngOnDestroy

C ngOnChanges

D ngAfterContentInit

ngAfterContentInit runs after content projection but before the view initialization, so it runs just before ngAfterViewInit.

Explain in your own words why ngAfterViewInit is the right place to access DOM elements or child components in Angular.

Think about when the view is ready to be used.

Describe a scenario where updating a property inside ngAfterViewInit causes an error and how to fix it.

Angular checks the view before and after lifecycle hooks.

Practice

1. What is the main purpose of the ngAfterViewInit lifecycle hook in Angular?

easy

A. To clean up resources when the component is destroyed

B. To initialize component input properties before the view loads

C. To handle user input events like clicks and keypresses

D. To run code after the component's view and child views are fully initialized

Solution

1. Step 1: Understand Angular lifecycle hooks

   Angular provides hooks to run code at specific times in a component's life, such as creation, view initialization, and destruction.

2. Step 2: Identify when ngAfterViewInit runs

   ngAfterViewInit runs after Angular fully initializes the component's view and its child views, making it safe to access view elements.

3. Final Answer:

   To run code after the component's view and child views are fully initialized -> Option D

4. Quick Check:

   ngAfterViewInit = view ready code [OK]

Hint: Runs after view loads, safe to access elements [OK]

Common Mistakes:

• Confusing it with ngOnInit which runs earlier
• Using it to handle input properties initialization
• Thinking it runs on component destruction

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

easy

A. ngAfterViewInit => { console.log('View initialized'); }

B. ngAfterViewInit() { console.log('View initialized'); }

C. function ngAfterViewInit() { console.log('View initialized'); }

D. ngAfterViewInit: function() { console.log('View initialized'); }

Solution

1. Step 1: Recall Angular component method syntax

   Angular lifecycle hooks are implemented as class methods without special syntax like arrow functions or function keywords.

2. Step 2: Check each option's syntax

   ngAfterViewInit() { console.log('View initialized'); } uses the correct method syntax inside a class. Options A, B, and C use invalid or incorrect JavaScript syntax for class methods.

3. Final Answer:

   ngAfterViewInit() { console.log('View initialized'); } -> Option B

4. Quick Check:

   Use method() syntax for lifecycle hooks [OK]

Hint: Use method() syntax inside class for hooks [OK]

Common Mistakes:

• Using arrow functions for lifecycle hooks
• Adding function keyword inside class
• Using object literal syntax instead of class methods

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

import { Component, ViewChild, ElementRef, AfterViewInit } from '@angular/core';

@Component({ selector: 'app-sample', template: `
Content
` })
export class SampleComponent implements AfterViewInit {
  @ViewChild('box') box!: ElementRef;

  ngAfterViewInit() {
    console.log(this.box.nativeElement.textContent);
  }
}

medium

A. Content

B. undefined

C. Error: box is undefined

D. null

Solution

1. Step 1: Understand @ViewChild and ngAfterViewInit

   @ViewChild gets a reference to the DOM element after the view initializes. ngAfterViewInit runs after the view is ready, so the element is accessible.

2. Step 2: Check what is logged

   The code logs this.box.nativeElement.textContent, which is the text inside the <div> with #box, which is "Content".

3. Final Answer:

   Content -> Option A

4. Quick Check:

   @ViewChild + ngAfterViewInit = element ready [OK]

Hint: Access @ViewChild only after ngAfterViewInit [OK]

Common Mistakes:

• Trying to access @ViewChild in ngOnInit causing undefined
• Assuming @ViewChild is null before view init
• Confusing nativeElement with the ElementRef itself

4. What is the problem with this Angular component code?

import { Component, ViewChild, ElementRef, AfterViewInit } from '@angular/core';

@Component({ selector: 'app-test', template: `
Paragraph
` })
export class TestComponent implements AfterViewInit {
  @ViewChild('para') para!: ElementRef;

  ngOnInit() {
    console.log(this.para.nativeElement.textContent);
  }

  ngAfterViewInit() {
    console.log('View initialized');
  }
}

medium

A. ngAfterViewInit should be named ngAfterContentInit

B. Missing import of AfterViewInit interface

C. Accessing @ViewChild in ngOnInit causes undefined error

D. Template reference variable #para is invalid

Solution

1. Step 1: Identify when @ViewChild is available

   @ViewChild references are set only after the view initializes, which happens after ngOnInit.

2. Step 2: Check code usage

   The code tries to access this.para.nativeElement.textContent inside ngOnInit, which runs before the view is ready, causing undefined or error.

3. Final Answer:

   Accessing @ViewChild in ngOnInit causes undefined error -> Option C

4. Quick Check:

   @ViewChild ready only after ngAfterViewInit [OK]

Hint: Use @ViewChild only in ngAfterViewInit or later [OK]

Common Mistakes:

• Accessing @ViewChild in ngOnInit
• Confusing ngAfterViewInit with ngOnInit timing
• Ignoring lifecycle hook order

5. You want to change the background color of a child component's element after it is fully rendered. Which approach correctly uses ngAfterViewInit to do this in the parent component?

Child component template:
<div #childBox>Child Content</div>

Parent component code options:

hard

A. Use @ViewChild('childBox') in parent and change style in ngAfterViewInit

B. Change child element style directly in parent's ngOnInit

C. Use @ViewChild in parent and change style in constructor

D. Modify child element style in parent's ngAfterContentInit without @ViewChild

Solution

1. Step 1: Understand when child view elements are ready

   Child component's view elements are accessible in the parent during ngAfterViewInit, after the parent's view and child views are fully initialized.

2. Step 2: Identify correct lifecycle hook and access method

   Using @ViewChild in the parent to get the child's element reference and modifying it in ngAfterViewInit ensures the element is ready and safe to modify.

3. Final Answer:

   Use @ViewChild('childBox') in parent and change style in ngAfterViewInit -> Option A

4. Quick Check:

   Modify child view in parent's ngAfterViewInit with @ViewChild [OK]

Hint: Use @ViewChild and ngAfterViewInit to access child elements [OK]

Common Mistakes:

• Trying to access child elements in ngOnInit or constructor
• Modifying child elements without @ViewChild reference
• Using ngAfterContentInit which is for projected content, not view