Why component communication matters in Angular - Quick Recap

Recall & Review

beginner

What is component communication in Angular?

Component communication is how different parts (components) of an Angular app share data and interact with each other to work together smoothly.

beginner

Why do Angular components need to communicate?

Because components are like pieces of a puzzle, they need to share information to build the full picture and respond to user actions or data changes.

intermediate

Name two common ways Angular components communicate.

1. Using @Input() and @Output() decorators to pass data and events between parent and child components.
2. Using shared services to share data across unrelated components.

beginner

What happens if components don’t communicate properly?

The app can become confusing or broken because parts won’t update or respond correctly, like friends not talking and missing important info.

beginner

How does component communication improve user experience?

It keeps the app responsive and consistent by making sure all parts show the right data and react quickly to user actions.

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

A @Output()

B @Input()

C @Injectable()

D @Component()

The @Input() decorator allows a parent component to send data to its child component.

What is a common method to share data between unrelated Angular components?

A Using shared services

B Using @Input() only

C Using CSS styles

D Using HTML templates

Shared services let unrelated components share data by acting as a common source.

What role does @Output() play in component communication?

A It creates new components

B It passes data from parent to child

C It styles components

D It sends events from child to parent components

@Output() lets child components send events or messages back to their parent components.

Why is component communication important in Angular apps?

A To keep components working together and data updated

B To make the app load faster

C To change the app’s colors

D To write less code

Communication keeps components in sync and the app responsive to user actions.

If components don’t communicate, what might happen?

A The app will run faster

B The app will automatically fix itself

C Parts of the app may not update or respond correctly

D The app will use less memory

Without communication, components can show outdated info or ignore user actions.

Explain why component communication matters in Angular applications.

Think about how friends share information to work well together.

Describe two ways Angular components communicate and when you might use each.

Consider how family members talk directly vs. neighbors sharing news through a common place.

Practice

1. Why is component communication important in Angular applications?

easy

A. It helps components to load faster independently.

B. It allows components to share data and work together smoothly.

C. It prevents components from being reused.

D. It makes components run without Angular framework.

Solution

1. Step 1: Understand component roles

   Components often need to share data to build a complete UI.

2. Step 2: Recognize communication purpose

   Sharing data helps components work together smoothly and stay in sync.

3. Final Answer:

   It allows components to share data and work together smoothly. -> Option B

4. Quick Check:

   Component communication = sharing data [OK]

Hint: Communication means sharing data between components [OK]

Common Mistakes:

• Thinking components work best completely isolated
• Confusing communication with performance optimization
• Believing Angular runs components without communication

2. Which syntax correctly passes data from a parent to a child component in Angular?

easy

A. <child-comp *data="parentData"></child-comp>

B. <child-comp (data)="parentData"></child-comp>

C. <child-comp #data="parentData"></child-comp>

D. <child-comp [data]="parentData"></child-comp>

Solution

1. Step 1: Identify Angular input binding syntax

   Angular uses square brackets [] to bind data from parent to child.

2. Step 2: Match syntax to data passing

   [data]="parentData" correctly passes parentData to child's @Input() property.

3. Final Answer:

   <child-comp [data]="parentData"></child-comp> -> Option D

4. Quick Check:

   Parent to child uses [property] binding [OK]

Hint: Use square brackets [] for parent to child data [OK]

Common Mistakes:

• Using parentheses () which are for event binding
• Using template reference # incorrectly
• Using structural directive * wrongly

3. Given this parent and child component code, what will be logged when the child emits an event?

Child component TS:
@Output() notify = new EventEmitter<string>();
sendNotification() { this.notify.emit('Hello'); }

Parent component template:
<child-comp (notify)="onNotify($event)"></child-comp>

Parent component TS:
onNotify(message: string) { console.log(message); }

medium

A. Hello

B. undefined

C. Error: notify is not a function

D. No output

Solution

1. Step 1: Understand event emission

   The child emits 'Hello' via notify.emit('Hello').

2. Step 2: Check parent event binding

   The parent listens with (notify)="onNotify($event)", so onNotify receives 'Hello'.

3. Final Answer:

   Hello -> Option A

4. Quick Check:

   Child event emits 'Hello' caught by parent [OK]

Hint: Child emits event, parent listens with (event) binding [OK]

Common Mistakes:

• Confusing @Output with @Input
• Not passing $event in parent handler
• Expecting no output without calling emit

4. What is wrong with this Angular code for passing data from parent to child?

Parent template:
<child-comp data="parentData"></child-comp>

Child component TS:
@Input() data: string;

medium

A. The parent should use parentheses: (data)="parentData".

B. The child should use @Output() instead of @Input().

C. The parent should use square brackets: [data]="parentData".

D. The child should declare data as a function, not a property.

Solution

1. Step 1: Identify correct binding syntax

   Passing data from parent to child requires property binding with square brackets.

2. Step 2: Analyze given code

   Using data="parentData" passes a string literal, not the variable value.

3. Final Answer:

   The parent should use square brackets: [data]="parentData". -> Option C

4. Quick Check:

   Property binding needs [] around attribute [OK]

Hint: Use [] for passing variables, not quotes [OK]

Common Mistakes:

• Using string literals instead of variable binding
• Confusing @Input and @Output decorators
• Using event binding () for data input

5. You have two unrelated Angular components that need to share user login status. Which approach is best to communicate this data?

hard

A. Use a shared service with an observable to hold and broadcast the login status.

B. Pass data directly using @Input() and @Output() between the two components.

C. Use local variables inside each component without communication.

D. Use template reference variables to share data between components.

Solution

1. Step 1: Identify component relationship

   Unrelated components do not have parent-child relation, so @Input/@Output won't work.

2. Step 2: Choose communication method

   A shared service with an observable allows broadcasting data to any component.

3. Final Answer:

   Use a shared service with an observable to hold and broadcast the login status. -> Option A

4. Quick Check:

   Unrelated components communicate via shared service [OK]

Hint: Use shared service for unrelated component communication [OK]

Common Mistakes:

• Trying to use @Input/@Output between unrelated components
• Using local variables that don't share data
• Misusing template reference variables for communication