Why NgRx store concept in Angular? - Purpose & Use Cases

The Big Idea

Discover how a single source of truth can save your app from chaos!

The Scenario

Imagine building a large Angular app where many parts need to share and update data like user info, settings, or shopping cart items.

You try to pass data manually through many components or use simple services to keep track.

The Problem

Manually passing data around or using services can get messy fast.

It's easy to lose track of where data changes, causing bugs and inconsistent views.

Debugging becomes hard because state changes happen everywhere without a clear flow.

The Solution

NgRx store gives you one central place to keep your app's state.

It uses a clear pattern where state changes happen only through defined actions and reducers.

This makes data flow predictable, easier to debug, and components stay in sync automatically.

Before vs After

✗ Before

this.cartService.addItem(item);
this.cartItems = this.cartService.getItems();

✓ After

store.dispatch(addItem({ item }));
this.cartItems$ = store.select(selectCartItems);

What It Enables

It enables building scalable apps with predictable state management and easy debugging.

Real Life Example

Think of an online store where the shopping cart updates instantly everywhere you look, no matter which page or component you're on.

Key Takeaways

Manual data sharing gets complicated and error-prone in big apps.

NgRx store centralizes state with clear rules for updates.

This leads to predictable, maintainable, and bug-resistant apps.

Practice

1. What is the primary purpose of the NgRx Store in an Angular application?

easy

A. To style components with CSS dynamically

B. To handle HTTP requests and responses automatically

C. To keep all application data in one central place for easy access and updates

D. To manage routing between different pages

Solution

1. Step 1: Understand NgRx Store role

   The NgRx Store is designed to hold the application state in one place.

2. Step 2: Compare with other options

   Options B, C, and D describe other Angular features, not the store's purpose.

3. Final Answer:

   To keep all application data in one central place for easy access and updates -> Option C

4. Quick Check:

   NgRx Store = Central app data storage [OK]

Hint: NgRx Store = single source of truth for app data [OK]

Common Mistakes:

• Confusing store with routing or HTTP services
• Thinking store manages styles or UI directly

2. Which of the following is the correct way to dispatch an action named loadItems using NgRx Store in a component?

easy

A. this.store.call(loadItems);

B. this.store.emit(loadItems);

C. store.dispatch = loadItems();

D. this.store.dispatch(loadItems());

Solution

1. Step 1: Recall NgRx dispatch syntax

   Actions are dispatched by calling this.store.dispatch(action()).

2. Step 2: Check other options for syntax errors

   Options A, B, and C use incorrect methods or assignment instead of dispatch call.

3. Final Answer:

   this.store.dispatch(loadItems()); -> Option D

4. Quick Check:

   Dispatch action = this.store.dispatch(action()) [OK]

Hint: Dispatch actions with this.store.dispatch(action()) [OK]

Common Mistakes:

• Using emit or call instead of dispatch
• Assigning dispatch instead of calling it

3. Given this reducer snippet:

const initialState = { count: 0 };
function counterReducer(state = initialState, action) {
  switch(action.type) {
    case 'increment':
      return { count: state.count + 1 };
    case 'decrement':
      return { count: state.count - 1 };
    default:
      return state;
  }
}

What will be the state after dispatching { type: 'increment' } twice starting from initial state?

medium

A. { count: 0 }

B. { count: 2 }

C. { count: 1 }

D. { count: -2 }

Solution

1. Step 1: Analyze reducer behavior for 'increment'

   Each 'increment' action adds 1 to the current count.

2. Step 2: Apply two increments starting from 0

   0 + 1 = 1 after first increment, then 1 + 1 = 2 after second increment.

3. Final Answer:

   { count: 2 } -> Option B

4. Quick Check:

   Two increments = count 2 [OK]

Hint: Add 1 per 'increment' action to count [OK]

Common Mistakes:

• Counting only one increment
• Confusing decrement with increment

4. Identify the error in this NgRx reducer code:

function todoReducer(state = [], action) {
  if (action.type === 'add') {
    state.push(action.payload);
    return state;
  }
  return state;
}

medium

A. Mutating state directly instead of returning a new state

B. Missing default case in reducer

C. Incorrect action type string

D. Reducer should not return state

Solution

1. Step 1: Check state mutation

   The reducer uses state.push(), which changes the original array directly.

2. Step 2: Understand NgRx immutability rule

   Reducers must return new state objects without mutating the old state.

3. Final Answer:

   Mutating state directly instead of returning a new state -> Option A

4. Quick Check:

   Reducers must be pure and immutable [OK]

Hint: Never mutate state; always return new object/array [OK]

Common Mistakes:

• Using push instead of spread operator
• Ignoring immutability in reducers

5. You want to create a feature state slice for user profiles using NgRx. Which combination correctly sets up the feature state and selector?

1. Define interface UserProfileState { name: string; age: number; }
2. Create reducer userProfileReducer
3. Register feature state with key 'userProfile'
4. Select user name from store

Which code snippet correctly selects the user name?

hard

A. const selectUserProfile = createFeatureSelector<UserProfileState>('userProfile');
const selectUserName = createSelector(selectUserProfile, state => state.name);

B. const selectUserName = createSelector('userProfile', state => state.name);

C. const selectUserProfile = createSelector('userProfile');
const selectUserName = state => state.name;

D. const selectUserName = createFeatureSelector<UserProfileState>('userProfile').pipe(map(state => state.name));

Solution

1. Step 1: Understand feature selector usage

   Use createFeatureSelector with the feature key to get the feature state.

2. Step 2: Create selector for user name

   Use createSelector with the feature selector and a projector function to select the name.

3. Final Answer:

   const selectUserProfile = createFeatureSelector<UserProfileState>('userProfile'); const selectUserName = createSelector(selectUserProfile, state => state.name); -> Option A

4. Quick Check:

   Feature selector + createSelector = correct pattern [OK]

Hint: Use createFeatureSelector then createSelector for nested state [OK]

Common Mistakes:

• Passing string directly to createSelector
• Using pipe on selector instead of RxJS operators in component