Why state management matters in Angular - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a signal for managing a counter state.

Angular

const counter = [1](0);

Drag options to blanks, or click blank then click option'

Asignal

Bref

CuseState

Dstate

Attempts:

3 left

💡 Hint

Common Mistakes

Using React's useState instead of Angular's signal.

Using ref which is not an Angular concept.

Trying to use 'state' directly without signal.

In Angular signals, signal creates a reactive state holder.

2fill in blank

medium

Complete the code to update the counter signal by increasing its value by 1.

Angular

counter.[1](value => value + 1);

Drag options to blanks, or click blank then click option'

Aset

Bupdate

Cnext

Dchange

Attempts:

3 left

💡 Hint

Common Mistakes

Using set which replaces the value directly, not with a function.

Using next or change which are not Angular signal methods.

The update method changes the signal's value based on the current value.

3fill in blank

hard

Fix the error in the code to read the current value of the signal.

Angular

const currentValue = counter.[1];

Drag options to blanks, or click blank then click option'

Avalue

Bget

Ccurrent

Dread

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to call get() which does not exist.

Using current or read which are not valid properties.

Access the current value of a signal using its value property.

4fill in blank

hard

Fill both blanks to create a computed signal that doubles the counter value.

Angular

const doubleCounter = computed(() => counter.[1] * [2]);

Drag options to blanks, or click blank then click option'

Avalue

B2

C1

Dcounter

Attempts:

3 left

💡 Hint

Common Mistakes

Using counter directly without .value.

Multiplying by 1 which does not change the value.

Use counter.value to get the current count and multiply by 2 to double it.

5fill in blank

hard

Fill all three blanks to create a standalone component with a signal and a button to increment it.

Angular

import { Component, [1] } from '@angular/core';

@Component({
  selector: 'app-counter',
  standalone: true,
  template: `
    <button (click)="increment()">Increment</button>
    <p>Count: {{ '{{' }} counter.[2] {{'}}' }}</p>
  `
})
export class CounterComponent {
  counter = [3](0);

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

Drag options to blanks, or click blank then click option'

Asignal

Bvalue

Dcomputed

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting to import signal.

Using counter directly in template without .value.

Initializing counter with computed instead of signal.

Import signal to create the state. Use counter.value to display the current count. Initialize counter with signal(0).

Practice

1. Why is state management important in Angular applications?

easy

A. It helps keep app data consistent and updates smooth.

B. It makes the app load faster by skipping data updates.

C. It removes the need for components in the app.

D. It automatically writes all app code for you.

Solution

1. Step 1: Understand the role of state management

   State management tracks and updates data changes in the app to keep everything consistent.

2. Step 2: Identify the benefit in Angular apps

   It ensures smooth updates and reliable data flow between components.

3. Final Answer:

   It helps keep app data consistent and updates smooth. -> Option A

4. Quick Check:

   State management = consistent data and smooth updates [OK]

Hint: State management = smooth, consistent app data updates [OK]

Common Mistakes:

• Thinking it speeds up app load by skipping updates
• Believing it removes the need for components
• Assuming it writes code automatically

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

easy

A. const count = useSignal(0);

B. const count = new Signal(0);

C. const count = signal(0);

D. const count = createSignal(0);

Solution

1. Step 1: Recall Angular signal creation syntax

   Angular uses the function signal() to create reactive state variables.

2. Step 2: Match the correct syntax

   Only const count = signal(0); matches Angular's official pattern.

3. Final Answer:

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

4. Quick Check:

   Angular signal creation = signal() function [OK]

Hint: Use signal() function to create state in Angular [OK]

Common Mistakes:

• Using 'new Signal()' which is not Angular syntax
• Using 'useSignal()' which is React syntax
• Using 'createSignal()' which is from other frameworks

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. 0

D. Error

Solution

1. Step 1: Understand signal initialization and update

   The signal count starts at 0, then is updated to 5 using count.set(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: signal() returns current value when called like a function [OK]

Common Mistakes:

• Thinking count() returns initial value 0
• Expecting undefined because of missing parentheses
• Assuming set() does not update the value

4. What is wrong with this Angular state update code?

const user = signal({ name: 'Alice' });
user().name = 'Bob';
console.log(user().name);

medium

A. The signal should be created with new Signal(), not signal().

B. Directly modifying user().name does not update the signal state.

C. The console.log syntax is incorrect for signals.

D. Signals cannot hold objects as values.

Solution

1. Step 1: Identify how signals track changes

   Signals track changes only when set() is called; direct object property changes don't notify updates.

2. Step 2: Explain why direct mutation fails

   Changing user().name directly mutates the object but does not trigger signal reactivity.

3. Final Answer:

   Directly modifying user().name does not update the signal state. -> Option B

4. Quick Check:

   Signal state updates require set() calls [OK]

Hint: Always use set() to update signal state, not direct mutation [OK]

Common Mistakes:

• Thinking signals auto-detect object property changes
• Using new Signal() instead of signal()
• Believing signals can't hold objects

5. You want to keep track of a user's login status and update the UI reactively in Angular. Which approach best uses state management to achieve this?

hard

A. Use a global variable and manually refresh components when it changes.

B. Use a service without any reactive state to hold login info.

C. Store login status in localStorage and read it only on page load.

D. Create a signal for login status and update it with set() on login/logout events.

Solution

1. Step 1: Identify reactive state management for UI updates

   Using a signal to hold login status allows Angular to update UI automatically when state changes.

2. Step 2: Compare other options

   Global variables or localStorage do not provide reactive updates; services without reactive state miss automatic UI refresh.

3. Final Answer:

   Create a signal for login status and update it with set() on login/logout events. -> Option D

4. Quick Check:

   Reactive signals = automatic UI updates [OK]

Hint: Use signals with set() for reactive UI state changes [OK]

Common Mistakes:

• Using global variables without reactivity
• Relying only on localStorage without reactive updates
• Ignoring reactive services or signals