@Input decorator for parent to child in Angular - Performance & Optimization

Performance: @Input decorator for parent to child

MEDIUM IMPACT

This affects how data is passed and rendered between parent and child components, impacting rendering speed and interaction responsiveness.

Passing data from parent to child component efficiently

Angular

Parent template: <child-comp [data]="parentData" *ngIf="shouldShowChild"></child-comp>
Child component: @Input() data: any;

// Parent updates data only when necessary, uses OnPush change detection

Limits updates to child inputs and uses OnPush strategy to reduce unnecessary re-renders.

📈 Performance GainReduces change detection runs and re-renders, improving INP responsiveness

Passing data from parent to child component efficiently

Angular

Parent template: <child-comp [data]="parentData"></child-comp>
Child component: @Input() data: any;

// Parent updates parentData frequently even if child doesn't need it

Frequent updates to input data cause repeated change detection and re-rendering in the child, slowing interaction.

📉 Performance CostTriggers multiple change detection cycles and re-renders, increasing INP delay

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Frequent input updates without OnPush	Many DOM updates	Multiple reflows	High paint cost	[X] Bad
Input updates with OnPush and immutable data	Minimal DOM updates	Single reflow	Low paint cost	[OK] Good

Rendering Pipeline

When @Input data changes, Angular runs change detection on the child component, recalculates bindings, updates the DOM, and repaints affected parts.

→Change Detection

→Layout

→Paint

⚠️ BottleneckChange Detection triggers layout and paint if input changes affect the DOM

Core Web Vital Affected

INP

This affects how data is passed and rendered between parent and child components, impacting rendering speed and interaction responsiveness.

Optimization Tips

1Avoid frequent updates to @Input properties to reduce change detection overhead.

2Use OnPush change detection strategy in child components to optimize rendering.

3Pass immutable data objects to help Angular detect changes efficiently.

Performance Quiz - 3 Questions

What happens when a parent component frequently updates an @Input property without optimization?

A Child component ignores updates and stays static

B Child component runs change detection and re-renders often, slowing interaction

C Parent component slows down but child is unaffected

D Angular caches the input and skips updates automatically

DevTools: Performance

How to check: Record a performance profile while interacting with the parent component updating inputs; look for change detection and rendering times.

What to look for: Look for frequent change detection cycles and long scripting times indicating inefficient input updates.

Practice

1. What is the main purpose of the @Input decorator in Angular?

easy

A. To define a route in Angular

B. To send data from a child component to its parent component

C. To create a new Angular service

D. To allow a child component to receive data from its parent component

Solution

1. Step 1: Understand the role of @Input

   The @Input decorator is used to mark a property in a child component that can receive data from its parent.

2. Step 2: Compare options with the concept

   Only To allow a child component to receive data from its parent component correctly describes this data flow from parent to child. Options B, C, and D describe other unrelated Angular features.

3. Final Answer:

   To allow a child component to receive data from its parent component -> Option D

4. Quick Check:

   @Input passes data parent to child [OK]

Hint: Remember: @Input means data flows into child [OK]

Common Mistakes:

• Confusing @Input with @Output
• Thinking @Input sends data up to parent
• Mixing @Input with services or routing

2. Which of the following is the correct syntax to declare an @Input property named title in a child component?

easy

A. input title: string;

B. @Input() title: string;

C. @Output() title: string;

D. Input() title: string;

Solution

1. Step 1: Recall correct @Input syntax

   In Angular, to declare an input property, you use @Input() decorator before the property declaration.

2. Step 2: Check each option

   @Input() title: string; correctly uses @Input() with the property name and type. Options A and D miss the decorator syntax, and C uses @Output() which is for event emitters, not inputs.

3. Final Answer:

   @Input() title: string; -> Option B

4. Quick Check:

   Decorator syntax is @Input() [OK]

Hint: Always use @Input() decorator before property [OK]

Common Mistakes:

• Using @Output instead of @Input
• Forgetting parentheses after @Input
• Writing 'input' lowercase without decorator

3. Given the child component code:

@Component({ selector: 'child-comp', template: '{{name}}' })
export class ChildComponent {
  @Input() name!: string;
}

And the parent template:

<child-comp [name]="parentName"></child-comp>

If parentName = 'Angular', what will the child component display?

medium

A. Angular

B. parentName

C. {{name}}

D. Error: name not defined

Solution

1. Step 1: Understand data flow from parent to child

   The parent passes the string 'Angular' to the child's name property using property binding [name].

2. Step 2: Check child template rendering

   The child template displays {{name}}, which will be replaced by the value passed, 'Angular'.

3. Final Answer:

   Angular -> Option A

4. Quick Check:

   Parent value passed to child input = displayed text [OK]

Hint: Property binding passes parent data to child's @Input [OK]

Common Mistakes:

• Thinking the literal string 'parentName' is displayed
• Expecting template syntax {{name}} to show literally
• Assuming error because of missing initialization

4. Consider this child component code:

@Component({ selector: 'child-comp', template: '{{data}}' })
export class ChildComponent {
  @Input() data: string;
}

And parent template:

<child-comp data="parentData"></child-comp>

What is the problem here?

medium

A. The child property data must be initialized with a default value

B. The child component must use @Output instead of @Input

C. The parent should use property binding with square brackets: [data]

D. The parent should pass data using interpolation: {{parentData}}

Solution

1. Step 1: Identify how parent passes data to child input

   To pass a variable value from parent to child, Angular requires property binding syntax with square brackets, e.g., [data].

2. Step 2: Analyze the given parent template

   The parent uses data="parentData" without brackets, which passes the literal string 'parentData', not the variable's value.

3. Final Answer:

   The parent should use property binding with square brackets: [data] -> Option C

4. Quick Check:

   Use [inputProp] to pass variables [OK]

Hint: Use square brackets to bind variables to @Input [OK]

Common Mistakes:

• Passing variable names as strings without brackets
• Confusing @Input with @Output
• Thinking default initialization fixes binding errors

5. You have a parent component with a property user = {name: 'Alice', age: 30}. You want to pass only the name to a child component using @Input. Which is the best way to do this in the parent template?

hard

A. <child-comp [userName]="user.name"></child-comp>

B. <child-comp [userName]="user"></child-comp>

C. <child-comp userName="user.name"></child-comp>

D. <child-comp [userName]="user['age']"></child-comp>

Solution

1. Step 1: Understand the data to pass

   The parent wants to pass only the name property from the user object, not the whole object.

2. Step 2: Check each option for correct binding

   <child-comp [userName]="user.name"></child-comp> correctly binds user.name to the child's userName input. <child-comp [userName]="user"></child-comp> passes the whole object, not just the name. <child-comp userName="user.name"></child-comp> passes the string literal 'user.name' instead of the value. <child-comp [userName]="user['age']"></child-comp> passes the age, not the name.

3. Final Answer:

   <child-comp [userName]="user.name"></child-comp> -> Option A

4. Quick Check:

   Bind exact property with [inputProp]="object.prop" [OK]

Hint: Bind specific property with [inputProp]="object.prop" [OK]

Common Mistakes:

• Passing whole object instead of specific property
• Using quotes without brackets causing string literal
• Passing wrong property like age instead of name