Why signals are introduced in Angular

Introduction

Signals help Angular track changes in data easily and update the screen quickly. They make apps faster and simpler to build.

When you want your app to update parts of the screen automatically when data changes.

When you want to write cleaner code that reacts to changes without extra work.

When you want better performance by updating only what really needs to change.

When you want to avoid complex state management and make your app easier to understand.

Syntax

Angular

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

const count = signal(0);

count.set(1); // update value
const current = count(); // read value

Use signal(initialValue) to create a signal with a starting value.

Call the signal like a function count() to get its current value.

Examples

Create a signal for a name and update it. Reading the signal gives the current name.

Angular

const name = signal('Alice');
console.log(name()); // prints 'Alice'
name.set('Bob');
console.log(name()); // prints 'Bob'

Use update to change the signal value based on the old value.

Angular

const counter = signal(0);
counter.update(value => value + 1);
console.log(counter()); // prints 1

Sample Program

This Angular component uses a signal to keep track of a counter. When you click the button, the counter increases and the screen updates automatically.

Angular

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

@Component({
  selector: 'app-counter',
  standalone: true,
  template: `
    <h1>Counter: {{ counter() }}</h1>
    <button (click)="increment()">Add 1</button>
  `
})
export class CounterComponent {
  counter = signal(0);

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

Important Notes

Signals replace some complex change detection methods with a simpler reactive approach.

They help Angular know exactly what changed, so it updates only those parts of the UI.

Signals work well with Angular's new standalone components and modern patterns.

Summary

Signals make it easy to track and react to data changes.

They improve app speed by updating only what is needed.

Signals simplify writing reactive Angular code.

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