Effect for side effects in Angular - Mini Project: Build & Apply

Using Effect for Side Effects in Angular Signals

📖 Scenario: You are building a simple Angular standalone component that tracks a user's name and shows a greeting message. You want to log a message to the console every time the user's name changes, using Angular's effect function for side effects.

🎯 Goal: Create an Angular standalone component that uses a signal to store the user's name and an effect to log a message to the console whenever the name changes.

📋 What You'll Learn

Create a signal called userName with the initial value '' (empty string).

Create a signal called greeting that returns `Hello, ${userName()}`.

Use Angular's effect function to log `User name changed to: ${userName()}` whenever userName changes.

Create a standalone Angular component named UserGreetingComponent with a template that includes an input bound to userName and displays the greeting.

💡 Why This Matters

🌍 Real World

Using Angular signals and effects helps build reactive user interfaces that respond to user input and other changes efficiently.

💼 Career

Understanding Angular signals and effects is important for modern Angular development, especially for building clean, reactive components with side effects like logging or API calls.

1

Create the userName signal

Create a signal called userName with the initial value '' (empty string) inside the UserGreetingComponent.

Angular

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

@Component({
  selector: 'app-user-greeting',
  standalone: true,
  template: ``,
})
export class UserGreetingComponent {
  // Create userName signal here
}

Hint

Use signal('') to create a signal with an empty string.

2

Create the greeting signal

Inside UserGreetingComponent, create a signal called greeting that returns the string `Hello, ${userName()}` using an arrow function.

Angular

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

@Component({
  selector: 'app-user-greeting',
  standalone: true,
  template: ``,
})
export class UserGreetingComponent {
  userName = signal('');
  // Create greeting signal here
}

Hint

Use computed(() => `Hello, ${this.userName()}`) to create a computed signal.

3

Add an effect to log changes

Import effect from @angular/core and inside UserGreetingComponent create an effect that logs `User name changed to: ${userName()}` whenever userName changes.

Angular

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

@Component({
  selector: 'app-user-greeting',
  standalone: true,
  template: ``,
})
export class UserGreetingComponent {
  userName = signal('');
  greeting = computed(() => `Hello, ${this.userName()}`);
  // Add effect to log userName changes here
}

Hint

Use effect(() => { ... }) inside the constructor to watch userName.

4

Add template with input and greeting display

Add a template to UserGreetingComponent with an <input> element bound to userName using [ngModel] and (ngModelChange), and a <p> element that displays the greeting() signal.

Angular

import { Component, signal, computed, effect } from '@angular/core';
import { FormsModule } from '@angular/forms';

@Component({
  selector: 'app-user-greeting',
  standalone: true,
  imports: [FormsModule],
  template: `
    
  `,
})
export class UserGreetingComponent {
  userName = signal('');
  greeting = computed(() => `Hello, ${this.userName()}`);

  constructor() {
    effect(() => {
      console.log(`User name changed to: ${this.userName()}`);
    });
  }
}

Hint

Use [ngModel]="userName()" and (ngModelChange)="userName.set($event)" on the input, and display {{ greeting() }} in a paragraph.

Practice

1. What is the main purpose of an Effect in Angular?

easy

A. To style components with CSS dynamically

B. To define the main UI layout of a component

C. To handle user input events directly in the template

D. To run side tasks like data loading or logging when app state changes

Solution

1. Step 1: Understand what side effects mean in Angular

   Side effects are extra tasks like fetching data or logging that happen outside the main app logic.

2. Step 2: Identify the role of Effects

   Effects run these side tasks automatically when app state changes, keeping main logic clean.

3. Final Answer:

   To run side tasks like data loading or logging when app state changes -> Option D

4. Quick Check:

   Effect = side tasks on state change [OK]

Hint: Effects run extra tasks when app data changes [OK]

Common Mistakes:

• Thinking Effects handle UI layout
• Confusing Effects with event handlers
• Believing Effects style components

2. Which of the following is the correct way to create an Effect in Angular using RxJS operators?

easy

A. createEffect(() => this.actions$.subscribe(action => console.log(action)))

B. createEffect(() => this.actions$.map(action => action.type))

C. createEffect(() => this.actions$.pipe(ofType(loadData), tap(() => console.log('Loading'))))

D. createEffect(() => this.actions$.filter(action => action.type === 'loadData'))

Solution

1. Step 1: Recall the correct RxJS operators for Effects

   Effects use pipe with operators like ofType to filter actions and tap for side effects.

2. Step 2: Check each option's syntax

   createEffect(() => this.actions$.pipe(ofType(loadData), tap(() => console.log('Loading')))) correctly uses pipe, ofType, and tap. Others misuse operators or subscribe directly, which is incorrect inside Effects.

3. Final Answer:

   createEffect(() => this.actions$.pipe(ofType(loadData), tap(() => console.log('Loading')))) -> Option C

4. Quick Check:

   Effect uses pipe + ofType + tap [OK]

Hint: Use pipe with ofType and tap inside createEffect [OK]

Common Mistakes:

• Using subscribe inside createEffect
• Using map instead of tap for side effects
• Using filter without ofType

3. Given this Effect code snippet:

loadData$ = createEffect(() => this.actions$.pipe(
  ofType('LOAD_DATA'),
  tap(() => console.log('Data loading started'))
), { dispatch: false });

What will happen when the 'LOAD_DATA' action is dispatched?

medium

A. The message 'Data loading started' is logged, and no new action is dispatched

B. The message is logged and a new action is dispatched automatically

C. Nothing happens because dispatch is false

D. An error occurs because tap cannot be used here

Solution

1. Step 1: Understand the effect's dispatch option

   Setting dispatch: false means this Effect does not send out new actions after running.

2. Step 2: Analyze the tap operator

   The tap operator runs side code like logging but does not change or dispatch actions.

3. Final Answer:

   The message 'Data loading started' is logged, and no new action is dispatched -> Option A

4. Quick Check:

   dispatch false means no new action, tap logs side effect [OK]

Hint: dispatch: false means no new action dispatched [OK]

Common Mistakes:

• Assuming tap dispatches actions
• Thinking dispatch: false disables effect
• Confusing tap with map or switchMap

4. Identify the error in this Effect code:

saveData$ = createEffect(() => this.actions$.pipe(
  ofType('SAVE_DATA'),
  map(() => this.api.save()),
  tap(() => console.log('Save triggered'))
));

medium

A. Using map without returning an action causes an error

B. tap cannot be used after map

C. ofType should be replaced with filter

D. createEffect must not use arrow functions

Solution

1. Step 1: Check the map operator usage

   map must return a new action object for dispatching, but this.api.save() likely returns a Promise or void, not an action.

2. Step 2: Understand effect dispatch requirements

   Effects expect actions to be returned for dispatch unless dispatch: false is set, which is missing here.

3. Final Answer:

   Using map without returning an action causes an error -> Option A

4. Quick Check:

   map must return action for dispatch [OK]

Hint: map must return an action unless dispatch: false [OK]

Common Mistakes:

• Ignoring missing action return in map
• Thinking tap cannot follow map
• Confusing ofType with filter

5. You want to create an Effect that listens for a 'LOGIN' action, calls an async login API, and then dispatches either 'LOGIN_SUCCESS' or 'LOGIN_FAILURE' based on the result. Which code snippet correctly implements this?

hard

A. login$ = createEffect(() => this.actions$.pipe(
ofType('LOGIN'),
tap(() => this.authService.login()),
map(() => ({ type: 'LOGIN_SUCCESS' }))
));

B. login$ = createEffect(() => this.actions$.pipe(
ofType('LOGIN'),
switchMap(action => this.authService.login(action.credentials).pipe(
map(user => ({ type: 'LOGIN_SUCCESS', user })),
catchError(() => of({ type: 'LOGIN_FAILURE' }))
))
));

C. login$ = createEffect(() => this.actions$.pipe(
filter(action => action.type === 'LOGIN'),
map(() => this.authService.login()),
map(user => ({ type: 'LOGIN_SUCCESS', user }))
));

D. login$ = createEffect(() => this.actions$.pipe(
ofType('LOGIN'),
map(action => this.authService.login(action.credentials)),
map(user => ({ type: 'LOGIN_SUCCESS', user }))
));

Solution

1. Step 1: Identify async handling with switchMap

   Using switchMap allows calling the async login API and switching to its result stream.

2. Step 2: Handle success and error properly

   Inside switchMap, map creates a success action, and catchError returns a failure action wrapped in of to keep the stream alive.

3. Final Answer:

   login$ = createEffect(() => this.actions$.pipe( ofType('LOGIN'), switchMap(action => this.authService.login(action.credentials).pipe( map(user => ({ type: 'LOGIN_SUCCESS', user })), catchError(() => of({ type: 'LOGIN_FAILURE' })) )) )); -> Option B

4. Quick Check:

   Use switchMap + map + catchError for async effects [OK]

Hint: Use switchMap with map and catchError for async API calls [OK]

Common Mistakes:

• Using tap instead of switchMap for async calls
• Not handling errors with catchError
• Returning promises instead of observables