Why design patterns matter in Angular - See It in Action

Why Design Patterns Matter in Angular

📖 Scenario: You are building a simple Angular app that manages a list of tasks. To keep your code clean and easy to maintain, you will use a design pattern called the Singleton pattern to manage the task data in one place.

🎯 Goal: Build an Angular standalone service using the Singleton pattern to store and manage tasks, then use it in a component to display the tasks.

📋 What You'll Learn

Create a standalone Angular service called TaskService that holds a list of tasks.

Add a configuration variable maxTasks to limit the number of tasks.

Implement a method addTask in TaskService that adds a task only if the list has fewer than maxTasks.

Create a standalone Angular component called TaskListComponent that uses TaskService to display the tasks.

💡 Why This Matters

🌍 Real World

Managing shared data like tasks, user info, or settings in one place is common in real apps. Singleton services help keep data consistent and easy to update.

💼 Career

Understanding design patterns and Angular services is essential for building scalable, maintainable web applications in professional development.

1

Create the TaskService with initial tasks

Create a standalone Angular service called TaskService with a public property tasks initialized to an array containing exactly these strings: 'Buy groceries', 'Walk the dog', and 'Read a book'.

Angular

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

@Injectable({
  providedIn: 'root'
})
export class TaskService {
  tasks = ['Buy groceries', 'Walk the dog', 'Read a book'];
  // Your code here
}

Hint

Use @Injectable({ providedIn: 'root' }) to make the service a singleton.

2

Add a maxTasks configuration variable

Inside the TaskService, add a public property called maxTasks and set it to the number 5.

Angular

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

@Injectable({
  providedIn: 'root'
})
export class TaskService {
  tasks = ['Buy groceries', 'Walk the dog', 'Read a book'];
  // Add maxTasks property here
}

Hint

Just add maxTasks = 5; inside the class.

3

Add addTask method with maxTasks check

In TaskService, add a public method called addTask that takes a string parameter task. The method should add task to the tasks array only if the current number of tasks is less than maxTasks.

Angular

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

@Injectable({
  providedIn: 'root'
})
export class TaskService {
  tasks = ['Buy groceries', 'Walk the dog', 'Read a book'];
  maxTasks = 5;

  // Add addTask method here
}

Hint

Use this.tasks.length to check the current number of tasks.

4

Create TaskListComponent to display tasks

Create a standalone Angular component called TaskListComponent. Inject TaskService in its constructor. In the component template, use *ngFor to display each task from taskService.tasks inside a <li> element within a <ul>.

Angular

import { Component } from '@angular/core';
import { TaskService } from './task.service';

@Component({
  selector: 'app-task-list',
  standalone: true,
  template: `
    
      
    
  `
})
export class TaskListComponent {
  constructor(public taskService: TaskService) {}

  // Your code here
}

Hint

Use *ngFor="let task of taskService.tasks" inside the template to loop over tasks.

Practice

1. Why are design patterns important in Angular development?

easy

A. They automatically generate UI components without coding.

B. They make the app run faster by optimizing CPU usage.

C. They provide tested solutions to common problems, making code easier to maintain.

D. They replace the need for services and modules.

Solution

1. Step 1: Understand the purpose of design patterns

   Design patterns offer proven ways to solve common coding challenges, improving code quality.

2. Step 2: Relate to Angular app maintenance

   Using patterns helps keep Angular apps organized and easier to read and maintain over time.

3. Final Answer:

   They provide tested solutions to common problems, making code easier to maintain. -> Option C

4. Quick Check:

   Design patterns = tested solutions [OK]

Hint: Design patterns solve common problems simply [OK]

Common Mistakes:

• Thinking patterns speed up app performance directly
• Believing patterns auto-generate UI
• Confusing patterns with Angular modules

2. Which of the following is the correct way to implement a Singleton pattern in Angular?

easy

A. Declare variables inside ngOnInit() to keep them unique.

B. Create multiple instances of a component manually.

C. Use @Input() to share data between components.

D. Use a service with providedIn: 'root' to ensure a single instance.

Solution

1. Step 1: Recall Singleton pattern meaning

   Singleton means only one instance of a class exists throughout the app.

2. Step 2: Identify Angular way to create single instance

   Angular services with providedIn: 'root' are singletons by default.

3. Final Answer:

   Use a service with providedIn: 'root' to ensure a single instance. -> Option D

4. Quick Check:

   Singleton in Angular = service with providedIn root [OK]

Hint: Singleton = service with providedIn root [OK]

Common Mistakes:

• Thinking components are singletons by default
• Using @Input() for singleton behavior
• Declaring variables inside lifecycle hooks for singleton

3. Consider this Angular service using the Observer pattern:

import { Injectable } from '@angular/core';
import { Subject } from 'rxjs';

@Injectable({ providedIn: 'root' })
export class DataService {
  private dataSubject = new Subject<string>();
  data$ = this.dataSubject.asObservable();

  updateData(newData: string) {
    this.dataSubject.next(newData);
  }
}

What happens when updateData('Hello') is called?

medium

A. The data is stored but not sent to subscribers.

B. All subscribers to data$ receive the string 'Hello'.

C. Nothing happens until subscribe() is called inside updateData.

D. The service throws an error because Subject is private.

Solution

1. Step 1: Understand Subject and Observable

   Subject allows emitting values to all subscribers via next().

2. Step 2: Analyze updateData method

   Calling next('Hello') sends 'Hello' to all subscribers of data$ observable.

3. Final Answer:

   All subscribers to data$ receive the string 'Hello'. -> Option B

4. Quick Check:

   Subject.next() notifies subscribers [OK]

Hint: Subject.next() sends data to all subscribers [OK]

Common Mistakes:

• Confusing private property with access restrictions on next()
• Thinking subscribe() must be inside updateData
• Believing data is stored without notifying subscribers

4. This Angular code tries to implement the Observer pattern but has a bug:

import { Injectable } from '@angular/core';
import { Subject } from 'rxjs';

@Injectable({ providedIn: 'root' })
export class LoggerService {
  private logSubject = new Subject<string>();
  log$ = this.logSubject.asObservable();

  logMessage(message: string) {
    this.logSubject.next;
  }
}

What is the bug and how to fix it?

medium

A. The method calls next without parentheses; fix by adding ().

B. The Subject should be public, not private.

C. The service should not use Subject but BehaviorSubject.

D. The @Injectable decorator is missing a providedIn property.

Solution

1. Step 1: Identify the incorrect method call

   The code uses this.logSubject.next; which does not call the function.

2. Step 2: Correct the method call syntax

   It should be this.logSubject.next(message); with parentheses and argument.

3. Final Answer:

   The method calls next without parentheses; fix by adding (). -> Option A

4. Quick Check:

   Method call needs parentheses [OK]

Hint: Method calls need () to execute [OK]

Common Mistakes:

• Ignoring missing parentheses on method calls
• Changing Subject visibility unnecessarily
• Replacing Subject with BehaviorSubject without reason

5. You want to design an Angular app where multiple components react to user login status changes instantly. Which design pattern best fits this need and why?

hard

A. Observer pattern, because it lets components subscribe and react to login status updates.

B. Singleton pattern, because it creates multiple instances of login components.

C. Factory pattern, because it generates new login forms dynamically.

D. Decorator pattern, because it styles the login button differently.

Solution

1. Step 1: Understand the problem context

   Multiple components need to react instantly when login status changes.

2. Step 2: Match design pattern to behavior

   The Observer pattern allows components to subscribe to changes and update automatically.

3. Step 3: Evaluate other options

   Singleton ensures single instance but doesn't handle event updates; Factory creates objects; Decorator changes appearance.

4. Final Answer:

   Observer pattern, because it lets components subscribe and react to login status updates. -> Option A

5. Quick Check:

   Observer = subscribe and react to changes [OK]

Hint: Observer pattern = react to changes instantly [OK]

Common Mistakes:

• Confusing Singleton with event notification
• Using Factory for event handling
• Thinking Decorator changes behavior, not style