Why signals are introduced in Angular - See It in Action

Understanding Why Signals Are Introduced in Angular

📖 Scenario: You are building a simple Angular app that shows a counter. You want to update the counter value and see the changes immediately in the UI.Previously, Angular used complex change detection to update the UI. Now, Angular introduces signals to make this easier and faster.

🎯 Goal: Learn how to create and use a signal in Angular to update the UI reactively.Understand why signals help Angular apps perform better and have simpler code.

📋 What You'll Learn

Create a signal to hold a counter value

Create a function to update the counter

Bind the signal value to the template

Explain why signals improve Angular's reactivity

💡 Why This Matters

🌍 Real World

Signals help build fast and responsive Angular apps by making state changes easy to track and update in the UI.

💼 Career

Understanding signals is important for modern Angular development, improving app performance and code maintainability.

1

Create a signal to hold the counter value

In your Angular component, import signal from @angular/core. Then create a signal called counter with the initial value 0.

Angular

import { Component, signal } from '@angular/core';

@Component({
  selector: 'app-counter',
  template: `
    Counter: {{ counter() }}
  `
})
export class CounterComponent {
  // Create a signal called counter with initial value 0
  // Your code here
}

Hint

Use counter = signal(0) inside the component class.

2

Add a function to update the counter

Add a method called increment inside the CounterComponent class. This method should update the counter signal by adding 1 to its current value.

Angular

import { Component, signal } from '@angular/core';

@Component({
  selector: 'app-counter',
  template: `
    Counter: {{ counter() }}
  `
})
export class CounterComponent {
  counter = signal(0);

  // Add increment method to update counter
  // Your code here
}

Hint

Use this.counter.update(value => value + 1) inside the increment method.

3

Bind the increment method to a button in the template

Add a button inside the component template that calls the increment method when clicked. Use Angular's (click) event binding.

Angular

import { Component, signal } from '@angular/core';

@Component({
  selector: 'app-counter',
  template: `
    Counter: {{ counter() }}
    
    
  `
})
export class CounterComponent {
  counter = signal(0);

  increment() {
    this.counter.update(value => value + 1);
  }
}

Hint

Use <button (click)="increment()">Increment</button> inside the template.

4

Explain why signals improve Angular's reactivity

Add a comment inside the component class explaining that signals provide a simple and efficient way to track reactive state changes without complex change detection cycles.

Angular

import { Component, signal } from '@angular/core';

@Component({
  selector: 'app-counter',
  template: `
    Counter: {{ counter() }}
    Increment
  `
})
export class CounterComponent {
  counter = signal(0);

  increment() {
    this.counter.update(value => value + 1);
  }

  // Add a comment explaining why signals are introduced
  // Your code here
}

Hint

Write a comment starting with // Signals provide a simple and efficient way.

Practice

1. Why were signals introduced in Angular?

easy

A. To make it easier to track and react to data changes

B. To replace all Angular directives

C. To remove the need for components

D. To simplify CSS styling

Solution

1. Step 1: Understand the purpose of signals

   Signals help Angular track changes in data and update the UI efficiently.

2. Step 2: Compare with other options

   Replacing directives, removing components, or simplifying CSS are unrelated to signals.

3. Final Answer:

   To make it easier to track and react to data changes -> Option A

4. Quick Check:

   Signals improve data tracking = C [OK]

Hint: Signals help track data changes easily [OK]

Common Mistakes:

• Thinking signals replace Angular directives
• Confusing signals with styling tools
• Believing signals remove components

2. Which of the following is the correct way to create a signal in Angular?

easy

A. const count = createSignal(0);

B. const count = new Signal(0);

C. const count = signal(0);

D. const count = signal.create(0);

Solution

1. Step 1: Recall Angular signal syntax

   The correct syntax uses the function signal() to create a signal.

2. Step 2: Check other options

   Options B, C, and D use incorrect constructors or methods not in Angular's signal API.

3. Final Answer:

   const count = signal(0); -> Option C

4. Quick Check:

   Use signal() function to create signals = A [OK]

Hint: Use signal() function to create signals [OK]

Common Mistakes:

• Using new keyword with Signal
• Calling createSignal instead of signal
• Using dot notation like signal.create

3. Given this Angular code snippet:

const count = signal(0);
count.set(5);
console.log(count());

What will be printed in the console?

medium

A. 5

B. undefined

C. signal(0)

D. 0

Solution

1. Step 1: Understand signal creation and update

   The signal count starts at 0, then count.set(5) updates its value to 5.

2. Step 2: Evaluate the console.log output

   Calling count() returns the current value, which is 5 after the update.

3. Final Answer:

   5 -> Option A

4. Quick Check:

   Signal value after set(5) = 5 [OK]

Hint: Calling signal() returns current value [OK]

Common Mistakes:

• Thinking count() returns the initial value
• Confusing signal object with its value
• Expecting undefined without set call

4. What is wrong with this Angular signal code?

const count = signal(0);
count = signal(5);

medium

A. signal() cannot hold numbers

B. signal() must be called with a string

C. count() should be used instead of count

D. Signals cannot be reassigned like this

Solution

1. Step 1: Understand signal immutability

   Signals are constants; you cannot reassign the variable holding a signal.

2. Step 2: Check other options

   signal() accepts numbers, and count() is for reading value, not reassignment.

3. Final Answer:

   Signals cannot be reassigned like this -> Option D

4. Quick Check:

   Signal variables are constant references = A [OK]

Hint: Signals are constants; don't reassign them [OK]

Common Mistakes:

• Trying to reassign signal variables
• Confusing signal creation with value reading
• Thinking signal only accepts strings

5. How do signals improve Angular app performance compared to traditional change detection?

hard

A. By running change detection on the entire app every time

B. By updating only the parts of the UI that depend on changed data

C. By disabling all UI updates until manual refresh

D. By removing the need for templates

Solution

1. Step 1: Understand traditional change detection

   Traditional Angular runs change detection on many components, which can be slow.

2. Step 2: Understand signals' selective update

   Signals update only UI parts that depend on changed data, improving speed and efficiency.

3. Step 3: Evaluate options

   By updating only the parts of the UI that depend on changed data correctly describes signals' selective update. By disabling all UI updates until manual refresh is incorrect because signals do not disable UI updates.

4. Final Answer:

   By updating only the parts of the UI that depend on changed data -> Option B

5. Quick Check:

   Signals update only needed UI parts = B [OK]

Hint: Signals update only affected UI parts [OK]

Common Mistakes:

• Thinking signals disable UI updates
• Believing change detection runs everywhere always
• Assuming signals remove templates