When NgRx is overkill in Angular - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the Angular service for simple state management.

Angular

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

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

AComponent

BDirective

CNgModule

DInjectable

Attempts:

3 left

💡 Hint

Common Mistakes

Using @Component instead of @Injectable

Confusing NgModule with Injectable

The @Injectable decorator is used to create services for simple state management without NgRx.

2fill in blank

medium

Complete the code to create a simple state variable in the service.

Angular

export class CounterService {
  count = [1];
}

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

A'zero'

Bnull

C0

Dundefined

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'zero' as a string

Setting count to null or undefined

We initialize the count with 0 as a number, not a string or null.

3fill in blank

hard

Fix the error in the method that increments the count.

Angular

increment() {
  this.count [1] 1;
}

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

A==

B+=

C-=

D=

Attempts:

3 left

💡 Hint

Common Mistakes

Using = instead of +=

Using == which is a comparison

The += operator adds 1 to the current count value.

4fill in blank

hard

Fill both blanks to create a simple Angular component that uses the service.

Angular

constructor(private [1]: [2]) {}

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

AcounterService

BCounterService

CCounterComponent

DcounterComponent

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping variable and class names

Using component names instead of service

The constructor injects the service using a variable name and its class type.

5fill in blank

hard

Fill all three blanks to update the template to show count and a button to increment.

Angular

<p>Count: {{ [1].[2] }}</p>
<button (click)="[3]()">Increment</button>

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

AcounterService

Bcount

Cincrement

DCounterService

Attempts:

3 left

💡 Hint

Common Mistakes

Using class name instead of variable in template

Calling wrong method name

The template accesses the service variable and method via the injected variable name.

Practice

1. Which situation suggests that using NgRx might be overkill in an Angular app?

easy

A. The app has only a few simple components with minimal shared state.

B. The app has complex state interactions and many features.

C. The app requires undo/redo functionality and time-travel debugging.

D. The app needs to synchronize state across multiple modules.

Solution

1. Step 1: Understand NgRx purpose

   NgRx is designed for complex state management with many parts and interactions.

2. Step 2: Identify simple app characteristics

   If the app has only a few simple components and minimal shared state, NgRx adds unnecessary complexity.

3. Final Answer:

   The app has only a few simple components with minimal shared state. -> Option A

4. Quick Check:

   Simple app = NgRx overkill [OK]

Hint: Simple apps rarely need NgRx; prefer local state [OK]

Common Mistakes:

• Thinking NgRx is always needed for any shared state
• Confusing complex features with simple apps
• Assuming NgRx improves all apps regardless of size

2. Which of the following is the correct way to manage simple state without NgRx in Angular?

easy

A. Always create actions, reducers, and effects for every state change.

B. Use NgRx store even for one or two variables.

C. Use a service with BehaviorSubject to hold and share state.

D. Avoid services and use only component inputs and outputs.

Solution

1. Step 1: Recall simple state management methods

   For simple state, Angular services with BehaviorSubject provide easy shared state without NgRx complexity.

2. Step 2: Evaluate other options

   Creating full NgRx setup for every change or avoiding services is unnecessary or impractical for simple cases.

3. Final Answer:

   Use a service with BehaviorSubject to hold and share state. -> Option C

4. Quick Check:

   Simple state = service + BehaviorSubject [OK]

Hint: Use services with BehaviorSubject for simple shared state [OK]

Common Mistakes:

• Overusing NgRx for trivial state
• Ignoring services as a state solution
• Thinking inputs/outputs replace shared state

3. Consider this Angular component code snippet managing local state without NgRx:

export class CounterComponent {
  count = 0;

  increment() {
    this.count++;
  }
}

What will be the displayed count after calling increment() twice?

medium

A. 2

B. 1

C. 0

D. undefined

Solution

1. Step 1: Understand initial state and method

   The count starts at 0 and increment() adds 1 each call.

2. Step 2: Calculate after two increments

   After two calls, count = 0 + 1 + 1 = 2.

3. Final Answer:

   2 -> Option A

4. Quick Check:

   Two increments = count 2 [OK]

Hint: Increment twice adds 2 to initial count 0 [OK]

Common Mistakes:

• Forgetting to call increment twice
• Assuming count resets automatically
• Confusing initial value with updated value

4. You have this Angular service managing state without NgRx:

export class SimpleService {
  private data = 0;

  setData(value: number) {
    this.data = value;
  }

  getData() {
    return this.data;
  }
}

Why might this cause issues in a multi-component app?

medium

A. Because getData returns a number instead of an observable.

B. Because data is private and cannot be accessed directly.

C. Because setData does not return a value.

D. Because changes to data are not observable by components.

Solution

1. Step 1: Analyze state sharing method

   The service stores data privately and exposes getter/setter but no observable pattern.

2. Step 2: Identify problem with state updates

   Without observables, components won't react to changes automatically, causing stale views.

3. Final Answer:

   Because changes to data are not observable by components. -> Option D

4. Quick Check:

   Non-observable state = no automatic updates [OK]

Hint: State must be observable for components to update [OK]

Common Mistakes:

• Thinking private variable blocks access
• Believing return type causes update issues
• Confusing method return with state reactivity

5. You are building a small Angular app with a few components sharing a simple counter state. You consider using NgRx but worry about complexity. Which approach best balances simplicity and shared state management?

hard

A. Use local variables in each component and synchronize manually with events.

B. Use a shared service with a BehaviorSubject to hold the counter and update it.

C. Keep the counter state only inside one component and pass it via inputs/outputs.

D. Implement full NgRx store with actions, reducers, and effects for the counter.

Solution

1. Step 1: Assess app complexity and state needs

   Small app with simple shared counter needs easy shared state without heavy setup.

2. Step 2: Evaluate options for simplicity and sharing

   Shared service with BehaviorSubject allows reactive updates and simple code, avoiding NgRx overhead.

3. Final Answer:

   Use a shared service with a BehaviorSubject to hold the counter and update it. -> Option B

4. Quick Check:

   Simple shared state = service + BehaviorSubject [OK]

Hint: Use BehaviorSubject service for simple shared state, avoid NgRx [OK]

Common Mistakes:

• Choosing full NgRx for small apps
• Using only inputs/outputs for shared state
• Manually syncing local variables across components