@ContentChild and content projection in Angular

Introduction

@ContentChild helps you get a reference to something passed inside your component from outside. Content projection lets you put any content inside your component's tag, like putting a photo inside a frame.

You want to access or control a part of the content someone puts inside your component.

You build a reusable component that can show different content inside it.

You want to style or interact with projected content from the parent component.

You need to call a method or read a property of a child element projected inside your component.

Syntax

Angular

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

@Component({
  selector: 'my-frame',
  template: `<ng-content></ng-content>`
})
export class MyFrameComponent implements AfterContentInit {
  @ContentChild('insideRef') insideElement!: ElementRef;

  ngAfterContentInit() {
    // use insideElement here
  }
}

@ContentChild looks for a child element or directive inside the projected content.

Use ngAfterContentInit lifecycle hook to safely access the projected content reference.

Examples

Here, the paragraph has a template reference #insideRef that @ContentChild can find.

Angular

<my-frame>
  <p #insideRef>This is inside content</p>
</my-frame>

This gets the element with the template reference #insideRef inside the projected content.

Angular

@ContentChild('insideRef') insideElement: ElementRef;

This tag is where the projected content will appear inside your component's template.

Angular

<ng-content></ng-content>

Sample Program

This example shows a MyFrameComponent that projects any content inside a blue border box. It uses @ContentChild to get the paragraph inside and logs its text after content initializes.

Angular

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

@Component({
  selector: 'my-frame',
  template: `
    <div style="border: 2px solid blue; padding: 1rem;">
      <h3>Frame Component</h3>
      <ng-content></ng-content>
    </div>
  `
})
export class MyFrameComponent implements AfterContentInit {
  @ContentChild('insideRef') insideElement!: ElementRef;

  ngAfterContentInit() {
    console.log('Projected content text:', this.insideElement.nativeElement.textContent.trim());
  }
}

@Component({
  selector: 'app-root',
  template: `
    <my-frame>
      <p #insideRef>This text is projected inside the frame.</p>
    </my-frame>
  `
})
export class AppComponent {}

Important Notes

Always use ngAfterContentInit to access @ContentChild because the content is not ready before that.

If the projected content changes dynamically, consider using @ContentChildren or other strategies.

Content projection keeps your component flexible and reusable by letting others decide what to put inside.

Summary

@ContentChild gets a reference to a single element inside projected content.

Content projection lets you insert any content inside your component's tag using <ng-content>.

Use ngAfterContentInit to safely work with projected content references.

Practice

1. What does the Angular decorator @ContentChild do in a component?

easy

A. It projects content from the component into its parent.

B. It creates a new child component inside the template.

C. It gets a reference to a single element inside the projected content.

D. It listens to events emitted by child components.

Solution

1. Step 1: Understand content projection

   Content projection allows inserting external content inside a component using <ng-content>.

2. Step 2: Role of @ContentChild

   @ContentChild gets a reference to a single element or directive inside that projected content.

3. Final Answer:

   It gets a reference to a single element inside the projected content. -> Option C

4. Quick Check:

   @ContentChild = reference to projected element [OK]

Hint: Remember: @ContentChild targets projected content elements [OK]

Common Mistakes:

• Confusing @ContentChild with @ViewChild
• Thinking it creates new elements
• Assuming it projects content instead of referencing it

2. Which of the following is the correct syntax to use @ContentChild to get a reference to a template variable named myRef?

easy

A. @ContentChild('myRef') myElement!: ElementRef;

B. @ContentChild(myRef) myElement!: ElementRef;

C. @ContentChild(#myRef) myElement!: ElementRef;

D. @ContentChild(myRef, {static: true}) myElement!: ElementRef;

Solution

1. Step 1: Correct syntax for @ContentChild selector

   The selector must be a string matching the template variable name, so it should be quoted: 'myRef'.

2. Step 2: Static option usage

   Static option is optional and usually false by default; not required here.

3. Final Answer:

   @ContentChild('myRef') myElement!: ElementRef; -> Option A

4. Quick Check:

   Use quotes around template variable name in @ContentChild [OK]

Hint: Use quotes around template variable name in @ContentChild [OK]

Common Mistakes:

• Omitting quotes around the selector string
• Using # inside the selector string
• Confusing static option necessity

3. Given this component code:

@Component({ selector: 'child-comp', template: `` })
export class ChildComp {
  @ContentChild('proj') projElement!: ElementRef;

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

And usage:

Hello World

What will be logged to the console?

medium

A. Hello World

B. undefined

C. Error: projElement is undefined

D. Empty string

Solution

1. Step 1: Understand content projection and @ContentChild

   The <p #proj> is projected inside <ng-content>. @ContentChild('proj') gets its reference.

2. Step 2: ngAfterContentInit timing

   ngAfterContentInit runs after projected content is initialized, so projElement is defined and accessible.

3. Final Answer:

   Hello World -> Option A

4. Quick Check:

   Projected element text logged correctly [OK]

Hint: Use ngAfterContentInit to access projected content safely [OK]

Common Mistakes:

• Trying to access projElement before ngAfterContentInit
• Assuming @ContentChild does not find projected elements
• Confusing @ViewChild with @ContentChild

4. Consider this component code:

@Component({ selector: 'proj-comp', template: `` })
export class ProjComp {
  @ContentChild('item') itemRef!: ElementRef;

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

And usage:

Test

What problem will occur when running this code?

medium

A. Logs 'Test' correctly

B. Error because itemRef is undefined in ngOnInit

C. Syntax error due to missing decorator

D. Logs empty string

Solution

1. Step 1: Lifecycle hook timing for @ContentChild

   @ContentChild references are not available in ngOnInit; they become available in ngAfterContentInit.

2. Step 2: Accessing itemRef in ngOnInit

   Accessing itemRef in ngOnInit causes it to be undefined, leading to runtime error when accessing nativeElement.

3. Final Answer:

   Error because itemRef is undefined in ngOnInit -> Option B

4. Quick Check:

   Use ngAfterContentInit for @ContentChild access [OK]

Hint: Access @ContentChild only in ngAfterContentInit [OK]

Common Mistakes:

• Accessing @ContentChild in ngOnInit
• Assuming @ContentChild is available immediately
• Ignoring lifecycle hook order

5. You want to create a component that projects multiple paragraphs and highlights the first paragraph. Which approach correctly achieves this?

Options:
A) Use @ContentChildren('para') and highlight the first in the list.
B) Use @ContentChild('para') and add #para to the first paragraph only.
C) Use @ViewChild('para') inside the component template.
D) Use @ContentChild without a selector and highlight all paragraphs.

hard

A. Use @ContentChild without a selector and highlight all paragraphs.

B. Use @ContentChild('para') and add #para to the first paragraph only.

C. Use @ViewChild('para') inside the component template.

D. Use @ContentChildren('para') and highlight the first in the list.

Solution

1. Step 1: Understand multiple projected elements

   When projecting multiple elements with the same template variable, use @ContentChildren to get all references.

2. Step 2: Highlight the first paragraph

   @ContentChildren returns a QueryList; you can access the first element and apply highlight logic.

3. Final Answer:

   Use @ContentChildren('para') and highlight the first in the list. -> Option D

4. Quick Check:

   Multiple projected elements need @ContentChildren [OK]

Hint: Use @ContentChildren for multiple projected elements [OK]

Common Mistakes:

• Using @ContentChild for multiple elements
• Using @ViewChild for projected content
• Omitting selector in @ContentChild