Child to parent communication flow in Angular - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main way a child component sends data to its parent in Angular?

The child component uses an @Output property with an EventEmitter to send data to the parent component.

beginner

How do you declare an event in a child component to notify the parent?

You declare an @Output() eventName = new EventEmitter<type>(); in the child component class.

beginner

How does the parent component listen to events from the child component?

In the parent template, bind to the child's event like <child (eventName)="parentHandler($event)"></child>.

intermediate

Why is using @Output with EventEmitter better than directly accessing child properties?

It keeps components loosely coupled and follows Angular's unidirectional data flow, making the app easier to maintain.

beginner

What is the role of the $event object in child to parent communication?

$event carries the data emitted by the child component's EventEmitter and is received by the parent's event handler.

Which decorator is used in Angular to send data from a child to a parent component?

A @Output

B @Input

C @ViewChild

D @Injectable

The @Output decorator is used with EventEmitter to send data from child to parent.

What Angular class is used to emit events from a child component?

A Observable

B EventEmitter

C Subject

D Promise

EventEmitter is the class used to emit custom events in Angular components.

How does the parent component receive data from the child component's event?

A By using @Input in the parent

B By calling a method on the child component directly

C By binding to the child's event in the template using (eventName)

D By using a service only

The parent listens to the child's event by binding to it in the template with (eventName).

What does the $event variable represent in Angular event binding?

A The Angular lifecycle hook

B The parent component instance

C The child component's template

D The data emitted by the child component's event

$event holds the data sent from the child component's EventEmitter.

Which of these is NOT a recommended way to communicate from child to parent in Angular?

A Directly modifying parent properties from child

B Using event binding in the parent template

C Using @Output with EventEmitter

D Passing data via emitted events

Directly modifying parent properties from child breaks encapsulation and is not recommended.

Explain how a child component sends data to its parent in Angular. Include the decorators and classes involved.

Think about how events work in Angular templates.

Describe why using @Output and EventEmitter is a good practice for child to parent communication in Angular.

Consider component independence and data flow direction.

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