Smart and dumb component pattern in Angular - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

Identify the role of the smart component

In Angular's smart and dumb component pattern, what is the primary responsibility of the smart component?

A Handle data fetching and business logic, passing data down to dumb components

B Only display UI elements without any logic or data fetching

C Directly manipulate the DOM for UI updates

D Serve as a reusable UI widget without inputs or outputs

💡 Hint

Think about which component talks to services and manages data.

The smart component manages data and business logic, fetching or updating data and passing it to dumb components for display.

❓ state_output

intermediate

State management in dumb components

What is the expected behavior of a dumb component regarding state in the smart and dumb component pattern?

A Receive data via inputs and emit events without managing state internally

B Maintain its own internal state and fetch data from services

C Directly update the global application state

D Handle routing and navigation logic

💡 Hint

Consider how dumb components communicate with smart components.

Dumb components receive data through inputs and notify smart components of user actions via outputs, without managing state themselves.

📝 Syntax

advanced

Correct @Input and @Output usage in dumb components

Which option correctly defines a dumb component with an input property 'items' and an output event 'selected' in Angular?

A

import { Component, Input, Output, EventEmitter } from '@angular/core';
@Component({selector: 'app-list', template: ''})
export class ListComponent {
  @Input() items: string[];
  @Output() selected: EventEmitter<string> = new EventEmitter();
}

B

import { Component, Input, Output } from '@angular/core';
@Component({selector: 'app-list', template: ''})
export class ListComponent {
  @Input items: string[] = [];
  @Output selected = new EventEmitter<string>();
}

C

import { Component, Input, Output, EventEmitter } from '@angular/core';
@Component({selector: 'app-list', template: ''})
export class ListComponent {
  items: string[] = [];
  selected = new EventEmitter<string>();
}

D

import { Component, Input, Output, EventEmitter } from '@angular/core';
@Component({selector: 'app-list', template: ''})
export class ListComponent {
  @Input() items: string[] = [];
  @Output() selected = new EventEmitter<string>();
}

💡 Hint

Remember the correct syntax for decorators and property initialization.

Option D correctly uses @Input and @Output decorators with proper property initialization and typing.

🔧 Debug

advanced

Why does the dumb component not update on input change?

A dumb component receives an array input from a smart component. The smart component updates the array by pushing new items, but the dumb component's view does not update. What is the likely cause?

A The dumb component forgot to declare the input property with @Input decorator

B The dumb component does not detect changes because the array reference did not change

C The smart component did not emit an event to notify the dumb component

D Angular does not support arrays as inputs

💡 Hint

Think about how Angular detects changes in inputs.

Angular's change detection checks for new object references. Mutating the array without changing its reference means the dumb component won't detect the change.

🧠 Conceptual

expert

Benefits of separating smart and dumb components

Which of the following is NOT a benefit of using the smart and dumb component pattern in Angular?

A Improved reusability of dumb components across different parts of the app

B Clear separation of concerns between data handling and UI rendering

C Automatic performance optimization without manual change detection

D Easier unit testing by isolating UI from business logic

💡 Hint

Consider what the pattern helps with and what it does not do automatically.

The pattern improves reusability, testing, and separation of concerns but does not automatically optimize performance or change detection.

Practice

1. What is the main role of a smart component in Angular's smart and dumb component pattern?

easy

A. To handle user input events only

B. To only display data without logic

C. To manage data and business logic

D. To style the user interface

Solution

1. Step 1: Understand smart component responsibilities

   Smart components are designed to handle data fetching, state management, and business logic.

2. Step 2: Differentiate from dumb components

   Dumb components focus on displaying data and emitting events, not managing data or logic.

3. Final Answer:

   To manage data and business logic -> Option C

4. Quick Check:

   Smart component = data and logic [OK]

Hint: Smart components handle data and logic, dumb ones display only [OK]

Common Mistakes:

• Confusing dumb components as managing data
• Thinking smart components only display UI
• Assuming smart components handle styling only

2. Which of the following is the correct way to pass data from a smart component to a dumb component in Angular?

easy

A. Use a service to directly modify dumb component variables

B. @Output() data: any; in dumb component and bind in template

C. Use @ViewChild to access dumb component data

D. @Input() data: any; in dumb component and bind in template

Solution

1. Step 1: Identify data flow direction

   Data flows from smart to dumb components via inputs.

2. Step 2: Use Angular syntax for input binding

   Dumb components declare @Input() properties to receive data from parents.

3. Final Answer:

   @Input() data: any; -> Option D

4. Quick Check:

   Data to dumb = @Input() [OK]

Hint: Use @Input() to pass data down from smart to dumb [OK]

Common Mistakes:

• Using @Output() to pass data down instead of events up
• Trying to access dumb component data directly via ViewChild
• Modifying dumb component state via services without inputs

3. Given the following Angular code, what will be the output displayed by the dumb component?

/* Smart component template */
<app-dumb [title]="pageTitle" (clicked)="onClicked()"></app-dumb>

/* Smart component class */
pageTitle = 'Hello World';
onClicked() { console.log('Clicked!'); }

/* Dumb component template */
<h1>{{ title }}</h1>
<button (click)="clicked.emit()">Click Me</button>

/* Dumb component class */
@Input() title: string;
@Output() clicked = new EventEmitter<void>();

medium

A. Displays 'Hello World' and logs 'Clicked!' on button click

B. Displays nothing and logs 'Clicked!' on button click

C. Displays 'Hello World' but does not log anything

D. Throws an error because of missing @Output() decorator

Solution

1. Step 1: Analyze data binding from smart to dumb

   The smart component passes 'Hello World' via [title] input, so dumb displays it.

2. Step 2: Analyze event emission and handling

   The dumb component emits clicked event on button click, smart component listens and logs 'Clicked!'.

3. Final Answer:

   Displays 'Hello World' and logs 'Clicked!' on button click -> Option A

4. Quick Check:

   Input shows title, output triggers log [OK]

Hint: Input shows data, output triggers event handled by smart [OK]

Common Mistakes:

• Thinking dumb component logs directly
• Assuming missing decorators cause runtime error here
• Ignoring event binding from dumb to smart

4. Identify the error in this dumb component code that prevents it from emitting events to the smart component:

@Component({
  selector: 'app-dumb',
  template: `<button (click)="clicked.emit()">Click</button>`
})
export class DumbComponent {
  clicked = new EventEmitter<void>();
}

medium

A. EventEmitter should be imported from '@angular/core/testing'

B. Missing @Output() decorator on the clicked property

C. The template syntax for click event is incorrect

D. The clicked property should be a function, not EventEmitter

Solution

1. Step 1: Check event emitter declaration

   The clicked property must have @Output() decorator to emit events to parent.

2. Step 2: Verify imports and syntax

   EventEmitter is correctly imported from '@angular/core', template syntax is correct.

3. Final Answer:

   Missing @Output() decorator on the clicked property -> Option B

4. Quick Check:

   @Output() missing = no event emission [OK]

Hint: Always add @Output() to EventEmitter properties [OK]

Common Mistakes:

• Forgetting @Output() decorator
• Importing EventEmitter from wrong package
• Miswriting template event binding syntax

5. You want to refactor a large Angular component that mixes data fetching, logic, and UI display into smart and dumb components. Which approach best follows the smart and dumb component pattern?

hard

A. Create a smart component to fetch data and handle logic, pass data via @Input() to dumb components that only display UI and emit events

B. Move all logic and data fetching into dumb components and keep smart components only for styling

C. Combine smart and dumb components into one to reduce complexity

D. Use dumb components to fetch data and smart components to display UI

Solution

1. Step 1: Separate concerns by responsibility

   Smart components should handle data fetching and logic, dumb components focus on UI and user interaction.

2. Step 2: Use Angular bindings correctly

   Pass data from smart to dumb via @Input() and receive events via @Output().

3. Final Answer:

   Create a smart component to fetch data and handle logic, pass data via @Input() to dumb components that only display UI and emit events -> Option A

4. Quick Check:

   Smart = logic/data, Dumb = UI only [OK]

Hint: Smart handles data/logic; dumb handles UI and events [OK]

Common Mistakes:

• Putting logic in dumb components
• Merging smart and dumb components unnecessarily
• Reversing data flow direction