Child to parent communication flow in Angular - Mini Project: Build & Apply

Child to Parent Communication Flow in Angular

📖 Scenario: You are building a simple Angular app where a child component sends a message to its parent component. This is like a child telling a parent something important.

🎯 Goal: Create a child component that sends a message to its parent component using Angular's event system. The parent component will display the message it receives.

📋 What You'll Learn

Create a child component with a button that sends a message when clicked

Create a parent component that listens to the child's message event

Use Angular's @Output and EventEmitter for communication

Display the received message in the parent component's template

💡 Why This Matters

🌍 Real World

This pattern is common in Angular apps where child components need to notify parents about user actions or data changes, like a form input or button click.

💼 Career

Understanding child to parent communication is essential for building interactive Angular applications and collaborating with other developers on component design.

1

Create the child component with a message

Create a child component class named ChildComponent with a string property message set to 'Hello from Child'.

Angular

# Your code here to create ChildComponent with message property

Hint

Use export class ChildComponent and add a property message with the exact string.

2

Add an EventEmitter to the child component

In ChildComponent, import EventEmitter and Output from @angular/core. Create an @Output() property named messageEvent as a new EventEmitter<string>().

Angular

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

@Component({
  selector: 'app-child',
  template: ``,
})
export class ChildComponent {
  message = 'Hello from Child';
  // Add @Output() messageEvent here
  // Your code here
}

Hint

Remember to import EventEmitter and Output. Then create @Output() messageEvent = new EventEmitter<string>().

3

Emit the message on button click in child template

Add a button in the ChildComponent template that calls a method sendMessage() when clicked. Implement sendMessage() to emit message using messageEvent.emit(this.message).

Angular

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

@Component({
  selector: 'app-child',
  template: `
    
    
  `,
})
export class ChildComponent {
  message = 'Hello from Child';
  @Output() messageEvent = new EventEmitter();

  // Add sendMessage() method here
  // Your code here
}

Hint

Add a button with (click)="sendMessage()" and define sendMessage() to emit the message.

4

Receive and display the message in the parent component

Create a parent component class named ParentComponent with a string property receivedMessage initialized to an empty string. In its template, include the app-child selector and bind to (messageEvent) with a method receiveMessage($event). Implement receiveMessage(message: string) to set receivedMessage. Display receivedMessage in the parent template inside a <p> tag.

Angular

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

@Component({
  selector: 'app-parent',
  template: `
    
    
    
  `,
})
export class ParentComponent {
  receivedMessage = '';

  // Add receiveMessage method here
  // Your code here
}

Hint

Use <app-child (messageEvent)="receiveMessage($event)"></app-child> in the template and define receiveMessage to update receivedMessage.

Practice

1. What is the main Angular feature used for communication from a child component to its parent?

easy

A. Using ViewChild to access parent methods

B. Using @Input to send data

C. Using services with HttpClient

D. Using @Output with EventEmitter

Solution

1. Step 1: Understand child to parent communication

   Child components send data or events to parents using Angular's event system.

2. Step 2: Identify Angular feature for this

   @Output decorator with EventEmitter allows child to emit events the parent listens to.

3. Final Answer:

   Using @Output with EventEmitter -> Option D

4. Quick Check:

   Child to parent = @Output + EventEmitter [OK]

Hint: Child emits events with @Output and EventEmitter [OK]

Common Mistakes:

• Confusing @Input as child to parent communication
• Thinking services are needed for simple child to parent
• Using ViewChild to call parent methods directly

2. Which of the following is the correct syntax to declare an event emitter in a child component?

easy

A. notify = new EventEmitter<string>();

B. @Input() notify = new EventEmitter<string>();

C. @Output() notify = new EventEmitter<string>();

D. @Output notify = EventEmitter<string>();

Solution

1. Step 1: Recall correct decorator and initialization

   Event emitters must be decorated with @Output() and initialized with new EventEmitter<type>().

2. Step 2: Check each option

   @Output() notify = new EventEmitter<string>(); correctly uses @Output() and initializes the emitter. Others miss decorator, use wrong decorator, or wrong syntax.

3. Final Answer:

   @Output() notify = new EventEmitter<string>(); -> Option C

4. Quick Check:

   @Output() + new EventEmitter() = correct syntax [OK]

Hint: Always use @Output() with new EventEmitter() [OK]

Common Mistakes:

• Using @Input instead of @Output
• Forgetting parentheses after @Output
• Not initializing EventEmitter with new keyword

3. Given this child component code:

@Output() change = new EventEmitter<number>();
updateValue() {
  this.change.emit(42);
}

What will the parent component receive when updateValue() is called?

medium

A. An event with value 42

B. An event with value 'updateValue'

C. No event emitted

D. An error because emit needs a string

Solution

1. Step 1: Understand what emit does

   The emit method sends the given value (here 42) as an event payload to the parent.

2. Step 2: Check the emitted value type

   The emitter is typed as number and emits 42, so the parent receives 42.

3. Final Answer:

   An event with value 42 -> Option A

4. Quick Check:

   emit(42) sends 42 to parent [OK]

Hint: emit(value) sends that value to parent [OK]

Common Mistakes:

• Assuming emit sends method name instead of value
• Thinking emit requires string only
• Believing no event is sent without explicit subscription

4. Identify the error in this child component code snippet:

@Output notify = new EventEmitter<string>();
send() {
  this.notify.emit('hello');
}

medium

A. Missing parentheses after @Output decorator

B. EventEmitter should not have a type parameter

C. emit method cannot send strings

D. notify should be private

Solution

1. Step 1: Check @Output decorator syntax

   The @Output decorator requires parentheses: @Output().

2. Step 2: Verify other parts

   Type parameter on EventEmitter is allowed, emit can send strings, and notify can be public.

3. Final Answer:

   Missing parentheses after @Output decorator -> Option A

4. Quick Check:

   @Output() needs parentheses [OK]

Hint: Always write @Output() with parentheses [OK]

Common Mistakes:

• Omitting parentheses after @Output
• Thinking EventEmitter can't have types
• Assuming emit only accepts numbers

5. You want a child component to send a complex object to its parent when a button is clicked. Which approach correctly implements this?

Child component:
@Output() sendData = new EventEmitter<{id:number, name:string}>();

onClick() {
  const data = {id: 1, name: 'Test'};
  this.sendData.emit(data);
}

Parent component template:
<app-child (sendData)="handleData($event)"></app-child>

What should the parent component's handleData method look like?

hard

A. handleData(data: number) { console.log(data); }

B. handleData(data: {id: number; name: string}) { console.log(data.name); }

C. handleData(event: string) { console.log(event); }

D. handleData() { console.log('No data received'); }

Solution

1. Step 1: Understand emitted data type

   The child emits an object with id and name properties.

2. Step 2: Match parent handler parameter

   The parent method must accept an object matching the emitted type to access properties like name.

3. Final Answer:

   handleData(data: {id: number; name: string}) { console.log(data.name); } -> Option B

4. Quick Check:

   Parent handler param matches emitted object type [OK]

Hint: Parent handler param matches emitted object shape [OK]

Common Mistakes:

• Ignoring event parameter in handler
• Using wrong parameter type in handler
• Not accessing object properties correctly