Selectors for derived state in Angular - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a selector in Angular state management?

A selector is a pure function that extracts and derives specific pieces of state from the store. It helps components get only the data they need.

intermediate

Why use selectors for derived state instead of computing values directly in components?

Selectors centralize logic, improve performance by memoizing results, and keep components simple and focused on display.

intermediate

How do selectors improve performance in Angular applications?

Selectors memoize their output, so if the input state hasn't changed, they return the cached result without recalculating, reducing unnecessary work.

beginner

Show a simple example of a selector that derives the total price from a list of items in the state.

Example selector: <br>const selectItems = (state) => state.items;<br>const selectTotalPrice = createSelector(selectItems, items => items.reduce((sum, item) => sum + item.price, 0));

beginner

What Angular function is commonly used to create selectors for derived state?

The function createSelector from NgRx is used to compose selectors and derive new state values.

What does a selector in Angular typically do?

A Extracts and derives specific state data

B Modifies the state directly

C Handles HTTP requests

D Defines component templates

Selectors extract and derive specific pieces of state for components to use.

Which Angular function helps create memoized selectors?

A createSelector

B useEffect

C inject

D mapState

createSelector is used to build memoized selectors in Angular state management.

Why is memoization important in selectors?

A It encrypts the state data

B It caches results to avoid unnecessary recalculations

C It updates the UI automatically

D It deletes unused state

Memoization caches selector results to improve performance by skipping recalculations when inputs don't change.

Where should derived state logic ideally be placed in Angular apps?

A In HTML files

B Directly in component templates

C In service constructors

D Inside selectors

Derived state logic belongs in selectors to keep components clean and reusable.

What is a benefit of using selectors for derived state?

A Removes the need for state

B Makes components heavier

C Centralizes logic and improves code reuse

D Requires more HTTP calls

Selectors centralize and reuse logic, making code easier to maintain.

Explain what selectors are and why they are useful for derived state in Angular.

Think about how selectors help get specific data from the store efficiently.

Describe how you would create a selector to calculate a total value from a list in the state.

Focus on combining simple selectors to compute a new value.

Practice

1. What is the main purpose of using createSelector in Angular state management?

easy

A. To dispatch actions to the store

B. To directly modify the state values

C. To compute derived data from the state efficiently

D. To subscribe to HTTP requests

Solution

1. Step 1: Understand what createSelector does

   createSelector is used to create selectors that compute derived data from the state without modifying it.

2. Step 2: Differentiate from other store operations

   Modifying state or dispatching actions are done by reducers and actions, not selectors.

3. Final Answer:

   To compute derived data from the state efficiently -> Option C

4. Quick Check:

   Derived data = createSelector [OK]

Hint: Remember: selectors read and compute, not modify state [OK]

Common Mistakes:

• Confusing selectors with actions or reducers
• Thinking selectors modify state
• Assuming selectors handle side effects

2. Which of the following is the correct syntax to create a selector that derives the total count from a list in the state using createSelector?

easy

A. const selectTotal = createSelector(list => list.length, selectList);

B. const selectTotal = createSelector(selectList, list => list.length);

C. const selectTotal = createSelector(selectList, list => list.count);

D. const selectTotal = createSelector(selectList, list => list.size());

Solution

1. Step 1: Check the order of arguments in createSelector

   The first argument(s) are input selectors, followed by a projector function.

2. Step 2: Verify the projector function logic

   The projector function receives the selected data and returns the derived value. Using list.length correctly gets the count.

3. Final Answer:

   const selectTotal = createSelector(selectList, list => list.length); -> Option B

4. Quick Check:

   Input selectors first, then projector function [OK]

Hint: Input selectors first, projector function last in createSelector [OK]

Common Mistakes:

• Swapping input selectors and projector function order
• Using incorrect property like count or size()
• Calling methods instead of accessing properties

3. Given the following selectors:

const selectItems = (state) => state.items;
const selectCompletedItems = createSelector(selectItems, items => items.filter(item => item.done));

What will selectCompletedItems return if state.items is [{done: true}, {done: false}, {done: true}]?

medium

A. [{done: true}, {done: true}]

B. []

C. [{done: false}]

D. [{done: true}, {done: false}]

Solution

1. Step 1: Understand the input selector

   selectItems returns the full list of items from state.

2. Step 2: Apply the projector function filter

   The projector filters items where item.done is true, so it keeps only those objects.

3. Final Answer:

   [{done: true}, {done: true}] -> Option A

4. Quick Check:

   Filter done=true items = [{done:true}, {done:true}] [OK]

Hint: Filter returns only items matching condition [OK]

Common Mistakes:

• Including false done items in result
• Returning original list without filtering
• Confusing filter condition logic

4. Identify the error in this selector code:

const selectUsers = (state) => state.users;
const selectActiveUsers = createSelector(selectUsers, users => users.active);

medium

A. The projector function incorrectly accesses users.active instead of filtering

B. The input selector should return a property, not the whole state

C. createSelector requires at least two input selectors

D. The selector should be an async function

Solution

1. Step 1: Check the input selector

   selectUsers correctly returns state.users, which is valid.

2. Step 2: Analyze the projector function

   The projector accesses users.active, but users is likely an array, so it should filter or map, not access a property.

3. Final Answer:

   The projector function incorrectly accesses users.active instead of filtering -> Option A

4. Quick Check:

   Projector must handle data type correctly [OK]

Hint: Check if projector matches data type (array vs object) [OK]

Common Mistakes:

• Assuming users is an object, not an array
• Trying to access properties on arrays directly
• Misunderstanding projector function role

5. You want to create a selector that returns the number of completed tasks and the number of pending tasks from state.
Given:

const selectTasks = (state) => state.tasks;

Which of the following createSelector implementations correctly derives this data?

hard

A. const selectTaskCounts = createSelector(selectTasks, tasks => tasks.doneCount)

B. const selectTaskCounts = createSelector(selectTasks, tasks => { completed: tasks.filter(t => t.done).length, pending: tasks.filter(t => !t.done).length });

C. const selectTaskCounts = createSelector(selectTasks, tasks => [tasks.filter(t => t.done).length, tasks.filter(t => !t.done).length]);

D. const selectTaskCounts = createSelector(selectTasks, tasks => ({ completed: tasks.filter(t => t.done).length, pending: tasks.filter(t => !t.done).length }));

Solution

1. Step 1: Check the syntax of the projector function

   const selectTaskCounts = createSelector(selectTasks, tasks => ({ completed: tasks.filter(t => t.done).length, pending: tasks.filter(t => !t.done).length })); returns an object with properties completed and pending correctly using parentheses to return the object literal.

2. Step 2: Identify errors in other options

   const selectTaskCounts = createSelector(selectTasks, tasks => { completed: tasks.filter(t => t.done).length, pending: tasks.filter(t => !t.done).length }); lacks parentheses around the object, causing a syntax error. const selectTaskCounts = createSelector(selectTasks, tasks => [tasks.filter(t => t.done).length, tasks.filter(t => !t.done).length]); returns an array, not an object. const selectTaskCounts = createSelector(selectTasks, tasks => tasks.doneCount) accesses a non-existent property.

3. Final Answer:

   const selectTaskCounts = createSelector(selectTasks, tasks => ({ completed: tasks.filter(t => t.done).length, pending: tasks.filter(t => !t.done).length })); -> Option D

4. Quick Check:

   Use parentheses to return object literals in arrow functions [OK]

Hint: Wrap object in parentheses to return from arrow function [OK]

Common Mistakes:

• Missing parentheses around object literal
• Returning array instead of object
• Accessing undefined properties