Why Effects for side effects in Angular? - Purpose & Use Cases

The Big Idea

Discover how to make your app handle side tasks automatically and avoid messy, buggy code!

The Scenario

Imagine you have to manually watch for every change in your app's data and then write code to update the UI, fetch new data, or save changes to a server.

You have to add event listeners everywhere and carefully manage when and how these side tasks run.

The Problem

This manual approach is tiring and error-prone because you might forget to update something or cause unexpected bugs by running side tasks too often or too late.

It becomes hard to keep track of all these side effects as your app grows.

The Solution

Effects in Angular let you declare side effects separately and react automatically to changes in your app's state.

This keeps your code clean, predictable, and easier to maintain because side effects run only when needed.

Before vs After

✗ Before

store.subscribe(() => { if (store.state.changed) { fetchData(); } });

✓ After

createEffect(() => this.actions$.pipe(ofType(loadData), switchMap(() => fetchData())));

What It Enables

It enables automatic, clean, and reliable handling of side effects triggered by app state changes without cluttering your main logic.

Real Life Example

When a user clicks a button to load data, Effects automatically fetch the data from the server and update the app without you writing complex manual subscriptions.

Key Takeaways

Manual side effect handling is complex and error-prone.

Effects separate side effects from main logic for clarity.

They run automatically when app state changes, improving reliability.

Practice

1. What is the main purpose of Effects in Angular applications?

easy

A. To define routes in the application

B. To style components dynamically

C. To handle side tasks like data fetching or logging outside components

D. To manage component templates

Solution

1. Step 1: Understand the role of Effects

   Effects are designed to handle side effects such as data fetching or logging, which are tasks outside the component's direct responsibilities.

2. Step 2: Compare with other options

   Styling, template management, and routing are handled by other Angular features, not Effects.

3. Final Answer:

   To handle side tasks like data fetching or logging outside components -> Option C

4. Quick Check:

   Effects = side tasks handler [OK]

Hint: Effects manage side tasks outside components [OK]

Common Mistakes:

• Confusing Effects with component styling
• Thinking Effects manage routing
• Assuming Effects handle templates

2. Which of the following is the correct way to create an effect using Angular's createEffect function?

easy

A. const loadData$ = createEffect(() => { this.actions$.pipe(ofType(load), switchMap(() => fetchData())); });

B. const loadData$ = createEffect(() => this.actions$.pipe(ofType(load), switchMap(() => fetchData())));

C. const loadData$ = createEffect(this.actions$.pipe(ofType(load), switchMap(() => fetchData())));

D. const loadData$ = createEffect(() => this.actions$.pipe(ofType(load), map(() => fetchData())));

Solution

1. Step 1: Check the syntax of createEffect

   The createEffect function expects a function returning an observable, so it should be () => this.actions$.pipe(...).

2. Step 2: Verify operators used

   Using switchMap is correct for side effects that return new observables. const loadData$ = createEffect(() => this.actions$.pipe(ofType(load), switchMap(() => fetchData()))); uses this correctly.

3. Final Answer:

   const loadData$ = createEffect(() => this.actions$.pipe(ofType(load), switchMap(() => fetchData()))); -> Option B

4. Quick Check:

   createEffect needs a function returning observable [OK]

Hint: createEffect needs a function returning an observable [OK]

Common Mistakes:

• Passing observable directly instead of a function
• Using map instead of switchMap for async calls
• Not returning the observable inside createEffect

3. Given this effect code snippet:

loadData$ = createEffect(() => this.actions$.pipe(
  ofType(loadData),
  switchMap(() => this.api.getData()),
  map(data => loadDataSuccess({ data })),
  catchError(() => of(loadDataFailure()))
));

What happens when the loadData action is dispatched?

medium

A. The API call is ignored and no action is dispatched

B. The effect causes a syntax error and stops

C. Only loadDataFailure action is dispatched immediately

D. The API call is made, and on success, loadDataSuccess action is dispatched

Solution

1. Step 1: Understand the effect flow

   When loadData action is dispatched, the effect listens and triggers the API call via switchMap.

2. Step 2: Analyze success and error handling

   On success, map dispatches loadDataSuccess with data; on error, catchError dispatches loadDataFailure.

3. Final Answer:

   The API call is made, and on success, loadDataSuccess action is dispatched -> Option D

4. Quick Check:

   Effect triggers API and dispatches success or failure [OK]

Hint: Effects dispatch success or failure actions after API calls [OK]

Common Mistakes:

• Assuming no action is dispatched after API call
• Confusing map with catchError behavior
• Thinking effect causes syntax error

4. Identify the error in this effect code:

saveData$ = createEffect(() => this.actions$.pipe(
  ofType(saveData),
  switchMap(action => this.api.save(action.payload)),
  map(() => saveDataSuccess()),
  catchError(error => saveDataFailure({ error }))
));

medium

A. The catchError operator should return an observable

B. The switchMap should not use action parameter

C. The map operator must return the original action

D. The effect should not use createEffect function

Solution

1. Step 1: Check catchError usage

   The catchError operator must return an observable, but here it returns an action object directly.

2. Step 2: Correct catchError return

   Wrapping the action in of() makes it an observable, fixing the error.

3. Final Answer:

   The catchError operator should return an observable -> Option A

4. Quick Check:

   catchError must return observable [OK]

Hint: Always wrap catchError return in of() to return observable [OK]

Common Mistakes:

• Returning plain object instead of observable in catchError
• Misusing switchMap parameters
• Thinking map must return original action

5. You want to create an effect that listens for login actions, calls an API to authenticate, and then dispatches either loginSuccess or loginFailure. Additionally, you want to log every login attempt regardless of success or failure. Which approach correctly implements this using Angular Effects?

hard

A. Use two separate effects: one for API call with dispatch, another for logging with dispatch: false

B. Use one effect with switchMap for API call and tap for logging inside the same pipe

C. Use one effect with map for API call and catchError for logging

D. Use one effect with filter to block logging and API call

Solution

1. Step 1: Separate concerns for side effects

   Logging is a side effect that does not dispatch actions, so it should be in a separate effect with dispatch: false.

2. Step 2: API call effect dispatches success or failure

   The main effect handles the API call and dispatches loginSuccess or loginFailure accordingly.

3. Step 3: Final design

   Two effects keep code clean and responsibilities clear: one for API calls with dispatch, one for logging without dispatch.

4. Final Answer:

   Use two separate effects: one for API call with dispatch, another for logging with dispatch: false -> Option A

5. Quick Check:

   Separate effects for dispatching and logging [OK]

Hint: Use separate effects for dispatching and non-dispatching tasks [OK]

Common Mistakes:

• Combining logging and dispatching in one effect incorrectly
• Using map instead of switchMap for API calls
• Forgetting dispatch: false for logging effect