ngAfterContentInit for projected content in Angular - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the lifecycle interface for content initialization.

Angular

import { Component, [1] } from '@angular/core';

Drag options to blanks, or click blank then click option'

AAfterViewInit

BOnInit

CAfterContentInit

DOnChanges

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing OnInit instead of AfterContentInit

Confusing AfterViewInit with AfterContentInit

The AfterContentInit interface is used to detect when projected content has been initialized.

2fill in blank

medium

Complete the code to implement the lifecycle hook method that runs after content projection.

Angular

export class ChildComponent implements AfterContentInit {
  [1]() {
    console.log('Content initialized');
  }
}

Drag options to blanks, or click blank then click option'

AngOnInit

BngAfterViewInit

CngOnChanges

DngAfterContentInit

Attempts:

3 left

💡 Hint

Common Mistakes

Using ngOnInit which runs earlier

Using ngAfterViewInit which runs after view initialization

The method ngAfterContentInit runs after Angular projects external content into the component.

3fill in blank

hard

Fix the error in the lifecycle hook method name to correctly detect projected content initialization.

Angular

export class SampleComponent implements AfterContentInit {
  ngAfterContent[1]() {
    console.log('Projected content ready');
  }
}

Drag options to blanks, or click blank then click option'

AInit

BIniting

CInitz

DInited

Attempts:

3 left

💡 Hint

Common Mistakes

Adding extra letters after 'Init'

Misspelling the method name

The correct method name is ngAfterContentInit exactly, with 'Init' at the end.

4fill in blank

hard

Fill both blanks to correctly use @ContentChild and detect when projected content is initialized.

Angular

import { Component, AfterContentInit, [1] } from '@angular/core';

@Component({
  selector: 'child-comp',
  template: '<ng-content></ng-content>'
})
export class ChildComponent implements AfterContentInit {
  @[2]('projectedRef') projectedElement: any;

  ngAfterContentInit() {
    console.log(this.projectedElement);
  }
}

Drag options to blanks, or click blank then click option'

AContentChild

BViewChild

CInput

DOutput

Attempts:

3 left

💡 Hint

Common Mistakes

Using @ViewChild instead of @ContentChild

Not importing ContentChild

The @ContentChild decorator is used to get a reference to projected content inside ngAfterContentInit.

5fill in blank

hard

Fill all three blanks to create a component that logs the text content of projected content after initialization.

Angular

import { Component, AfterContentInit, ContentChild, ElementRef } from '@angular/core';

@Component({
  selector: 'proj-comp',
  template: '<ng-content></ng-content>'
})
export class ProjComp implements AfterContentInit {
  @ContentChild('[1]') content!: ElementRef;

  ngAfterContentInit() {
    console.log(this.content.nativeElement.[2]);
  }
}

Drag options to blanks, or click blank then click option'

AprojectedContent

BtextContent

CinnerText

DcontentChild

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong selector string in @ContentChild

Trying to access a property that does not exist on nativeElement

The selector string for @ContentChild matches the template reference name. The textContent or innerText property gets the text inside the element.

Practice

1. What is the primary purpose of the ngAfterContentInit lifecycle hook in Angular?

easy

A. To run code after projected content has been inserted into the component

B. To initialize component input properties

C. To detect changes in component data bindings

D. To clean up resources before the component is destroyed

Solution

1. Step 1: Understand the role of ngAfterContentInit

   This hook runs after Angular projects external content into the component's <ng-content> slot.

2. Step 2: Identify when to use it

   It is used to safely access or manipulate the projected content once it is ready, not before.

3. Final Answer:

   To run code after projected content has been inserted into the component -> Option A

4. Quick Check:

   ngAfterContentInit = runs after projected content ready [OK]

Hint: Remember: ngAfterContentInit runs after content projection is done [OK]

Common Mistakes:

• Confusing ngAfterContentInit with ngOnInit
• Trying to access projected content before this hook
• Using it to detect input property changes

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

easy

A. ngAfterContentInit() { console.log('Content initialized'); }

B. ngAfterContentInit: () => { console.log('Content initialized'); }

C. ngAfterContentInit = function() { console.log('Content initialized'); }

D. function ngAfterContentInit() { console.log('Content initialized'); }

Solution

1. Step 1: Recall Angular lifecycle hook syntax

   Lifecycle hooks are implemented as methods on the component class without assignment or arrow functions.

2. Step 2: Check each option

   ngAfterContentInit() { console.log('Content initialized'); } uses the correct method syntax. Arrow functions or assignments are not valid lifecycle hook implementations. A standalone function is not a class method.

3. Final Answer:

   ngAfterContentInit() { console.log('Content initialized'); } -> Option A

4. Quick Check:

   Lifecycle hooks are class methods, not arrow functions [OK]

Hint: Use method syntax without arrow functions for lifecycle hooks [OK]

Common Mistakes:

• Using arrow functions for lifecycle hooks
• Defining lifecycle hooks outside the class
• Assigning lifecycle hooks to variables

3. Given the following Angular component code, what will be logged to the console when the component is initialized?

import { Component, AfterContentInit, ContentChild, ElementRef } from '@angular/core';

@Component({
  selector: 'child-comp',
  template: ``
})
export class ChildComp implements AfterContentInit {
  @ContentChild('projected') projectedContent!: ElementRef;

  ngAfterContentInit() {
    console.log(this.projectedContent.nativeElement.textContent.trim());
  }
}

// Usage in parent template:
// 
Hello World

medium

A. Error: Cannot read property 'nativeElement' of undefined

B. undefined

C. Hello World

D. Empty string

Solution

1. Step 1: Understand ContentChild and ngAfterContentInit

   The @ContentChild('projected') decorator gets the element with template reference #projected projected inside <ng-content>. This is available after content initialization.

2. Step 2: Check what ngAfterContentInit logs

   It logs the trimmed text content of the projected element, which is 'Hello World'.

3. Final Answer:

   Hello World -> Option C

4. Quick Check:

   ContentChild element text = 'Hello World' [OK]

Hint: ContentChild is ready in ngAfterContentInit, so text logs correctly [OK]

Common Mistakes:

• Trying to access ContentChild before ngAfterContentInit
• Forgetting to use template reference variable
• Assuming projected content is undefined

4. Consider this Angular component code snippet:

import { Component, AfterContentInit, ContentChild, ElementRef } from '@angular/core';

@Component({
  selector: 'proj-comp',
  template: ``
})
export class ProjComp implements AfterContentInit {
  @ContentChild('contentRef') content!: ElementRef;

  ngAfterContentInit() {
    console.log(this.content.nativeElement.textContent);
  }
}

When used as <proj-comp><p>Test</p></proj-comp>, what error will occur and why?

medium

A. Error: ngAfterContentInit is not called

B. Error: content is undefined because no template reference variable 'contentRef' is present

C. No error; logs 'Test' correctly

D. Error: nativeElement is not accessible

Solution

1. Step 1: Analyze ContentChild selector

   The @ContentChild('contentRef') looks for an element with template reference variable #contentRef inside projected content.

2. Step 2: Check usage in parent template

   The projected <p>Test</p> has no #contentRef variable, so content is undefined.

3. Step 3: Understand consequence in ngAfterContentInit

   Accessing this.content.nativeElement causes a runtime error because content is undefined.

4. Final Answer:

   Error: content is undefined because no template reference variable 'contentRef' is present -> Option B

5. Quick Check:

   Missing template ref causes undefined ContentChild [OK]

Hint: ContentChild needs matching template ref; else undefined error [OK]

Common Mistakes:

• Assuming ContentChild finds elements without template refs
• Ignoring runtime errors from undefined properties
• Confusing ngAfterContentInit with ngOnInit timing

5. You want to create a component that projects a list of items and highlights the first projected item after content initialization. Which approach correctly uses ngAfterContentInit to achieve this?

import { Component, AfterContentInit, ContentChildren, QueryList, ElementRef } from '@angular/core';

@Component({
  selector: 'highlight-list',
  template: ``
})
export class HighlightList implements AfterContentInit {
  @ContentChildren('item') items!: QueryList<ElementRef>;

  ngAfterContentInit() {
    // What should go here?
  }
}

Options for ngAfterContentInit implementation:

hard

A. document.querySelector('item').style.backgroundColor = 'yellow';

B. this.items.nativeElement.style.backgroundColor = 'yellow';

C. this.items[0].nativeElement.style.backgroundColor = 'yellow';

D. this.items.first.nativeElement.style.backgroundColor = 'yellow';

Solution

1. Step 1: Understand ContentChildren and QueryList

   @ContentChildren('item') collects all projected elements with template ref #item into a QueryList. Access the first element with items.first.

2. Step 2: Apply style to first projected item

   Use items.first.nativeElement.style.backgroundColor to highlight the first item safely after content is initialized.

3. Step 3: Evaluate other options

   this.items.nativeElement.style.backgroundColor = 'yellow'; is invalid because QueryList has no nativeElement property. this.items[0].nativeElement.style.backgroundColor = 'yellow'; is invalid because QueryList is not an array. document.querySelector('item').style.backgroundColor = 'yellow'; uses direct DOM query which breaks Angular encapsulation.

4. Final Answer:

   this.items.first.nativeElement.style.backgroundColor = 'yellow'; -> Option D

5. Quick Check:

   Use QueryList.first to access first projected element [OK]

Hint: Use QueryList.first, not array or direct DOM, to access projected items [OK]

Common Mistakes:

• Treating QueryList as an array
• Using direct DOM queries instead of Angular references
• Accessing nativeElement on QueryList itself