Why operators transform data streams in Angular - Challenge Your Understanding

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this Angular signal transformation?

Consider this Angular component using signals and operators. What will be the displayed value after the button is clicked twice?

Angular

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

@Component({
  selector: 'app-counter',
  standalone: true,
  template: `
    <p>Count: {{ doubled() }}</p>
    <button (click)="increment()">Increment</button>
  `
})
export class CounterComponent {
  count = signal(0);
  doubled = this.count.map(x => x * 2);

  increment() {
    this.count.update(c => c + 1);
  }
}

A Count: 0

B Count: 2

C Count: 1

D Count: 4

💡 Hint

Remember the operator doubles the count signal value each time it changes.

The count signal starts at 0. Each click increments it by 1. After two clicks, count is 2. The doubled signal maps count to count * 2, so 2 * 2 = 4.

📝 Syntax

intermediate

Which option correctly applies a map operator to an Angular signal?

Which code snippet correctly creates a new signal that doubles the original signal's value using the map operator?

A const doubled = originalSignal.map(x => x * 2);

B const doubled = map(originalSignal, x => x * 2);

C const doubled = originalSignal.pipe(map(x => x * 2));

D const doubled = originalSignal.transform(x => x * 2);

💡 Hint

Angular signals have a map method to create derived signals.

In Angular signals, map is a method on the signal instance that returns a new signal with transformed values. The other options use RxJS or invalid syntax.

🔧 Debug

advanced

Why does this Angular signal transformation cause a runtime error?

Given this code, why does it throw an error when the component renders?

Angular

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

@Component({
  selector: 'app-test',
  standalone: true,
  template: `{{ transformed() }}`
})
export class TestComponent {
  base = signal(5);
  transformed = this.base.map(x => {
    if (x > 3) throw new Error('Value too high');
    return x * 2;
  });
}

A Because signals cannot throw errors inside map functions

B Because the map operator runs synchronously and throws when x > 3

C Because the template syntax is invalid for signals

D Because the base signal is not initialized properly

💡 Hint

Think about when the map function executes and what happens if it throws.

The map function runs immediately when the signal value changes. If it throws an error, the component rendering fails with that error.

❓ state_output

advanced

What is the final value of the signal after these updates and transformations?

Given this Angular component code, what is the final value of result() after calling updateValues()?

Angular

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

@Component({
  selector: 'app-transform',
  standalone: true,
  template: `Result: {{ result() }}`
})
export class TransformComponent {
  base = signal(1);
  result = this.base.map(x => x + 3);

  updateValues() {
    this.base.set(2);
    this.base.update(x => x * 5);
  }
}

A Result: 13

B Result: 8

C Result: 6

D Result: 10

💡 Hint

Remember that update uses the current signal value after set.

After set(2), base is 2. Then update(x => x * 5) changes base to 10. The result signal maps base + 3, so 10 + 3 = 13.

🧠 Conceptual

expert

Why do operators like map transform data streams in Angular signals?

Which statement best explains why operators such as map are used to transform data streams in Angular signals?

A They modify the original signal's value directly to improve performance.

B They delay the signal updates until a manual refresh is triggered.

C They create new signals that automatically update when the original signal changes, enabling reactive data flow.

D They convert signals into promises to handle asynchronous data.

💡 Hint

Think about how reactive programming works with signals and derived values.

Operators like map create new signals derived from existing ones. These derived signals update automatically when the original changes, supporting reactive programming.