Redux selectors in React Native - UI Render Trace

Component - Redux selectors

This UI component shows how Redux selectors help get specific data from the app's state in a React Native app. It displays a list of items from the store and updates when the store changes.

Widget Tree

App
├── Provider
│   └── ItemList
│       ├── View
│       │   ├── Text (Title)
│       │   └── FlatList
│       │       └── renderItem -> Text (Item name)
│       └── Button (Refresh)

The root App uses Provider to give Redux store access. Inside, ItemList component renders a View containing a title Text, a FlatList showing items from the store, and a Button to refresh data.

Render Trace - 4 Steps

Step 1: Provider

Step 2: ItemList

Step 3: FlatList

Step 4: Button

State Change - Re-render

Trigger:User taps the 'Refresh' button

Before

items array contains initial list of items

→

After

items array updated with new or refreshed items

Re-renders:ItemList component and its children re-render to show updated items list

UI Quiz - 3 Questions

What does the useSelector hook do in the ItemList component?

A It extracts specific data from the Redux store using a selector function

B It dispatches actions to update the Redux store

C It provides the Redux store to the app components

D It renders the list of items on the screen

Key Insight

Using Redux selectors in React Native helps keep UI components simple and focused by separating data retrieval from UI logic. This makes the app more efficient and easier to maintain, as components only re-render when the selected data changes.

Practice

1. What is the main purpose of a Redux selector in a React Native app?

easy

A. To create UI components

B. To extract specific data from the Redux store state

C. To define the initial state of the store

D. To dispatch actions to update the store

Solution

1. Step 1: Understand Redux store role

   The Redux store holds the entire app state in one place.

2. Step 2: Role of selectors

   Selectors are functions that pick specific parts of that state for use in components.

3. Final Answer:

   To extract specific data from the Redux store state -> Option B

4. Quick Check:

   Selector = extract data [OK]

Hint: Selectors pick data from state, not change it [OK]

Common Mistakes:

• Confusing selectors with action creators
• Thinking selectors update state
• Using selectors to create UI components

2. Which of the following is the correct syntax to define a simple Redux selector function named selectUser that returns state.user?

easy

A. const selectUser = () => state.user;

B. const selectUser = (state) => { state.user }

C. function selectUser() { return user; }

D. const selectUser = state => state.user;

Solution

1. Step 1: Check function parameter

   A selector receives the whole state as an argument, so it must have state parameter.

2. Step 2: Check return statement

   The selector returns state.user directly. Arrow function with implicit return is correct.

3. Final Answer:

   const selectUser = state => state.user; -> Option D

4. Quick Check:

   Arrow function with state param and return [OK]

Hint: Selector must take state and return part of it [OK]

Common Mistakes:

• Omitting the state parameter
• Not returning the value properly
• Using braces without return statement

3. Given the selector const selectCompletedTodos = state => state.todos.filter(todo => todo.completed); and the state { todos: [{id:1, completed:true}, {id:2, completed:false}, {id:3, completed:true}] }, what will selectCompletedTodos(state) return?

medium

A. [{id:1, completed:true}, {id:3, completed:true}]

B. [{id:2, completed:false}]

C. []

D. undefined

Solution

1. Step 1: Understand selector logic

   The selector filters todos where completed is true.

2. Step 2: Apply filter to given state

   Todos with id 1 and 3 have completed:true, so they are included.

3. Final Answer:

   [{id:1, completed:true}, {id:3, completed:true}] -> Option A

4. Quick Check:

   Filter completed todos = correct list [OK]

Hint: Filter returns only items matching condition [OK]

Common Mistakes:

• Selecting incomplete todos instead
• Returning empty array by mistake
• Confusing filter with map

4. What is wrong with this selector code?

const selectUserName = state => { state.user.name }

medium

A. It does not return any value explicitly

B. It uses wrong parameter name

C. It should dispatch an action instead

D. It should be a class method

Solution

1. Step 1: Check function body

   The function uses braces but no return statement, so it returns undefined.

2. Step 2: Fix by adding return

   Either remove braces or add return to return state.user.name.

3. Final Answer:

   It does not return any value explicitly -> Option A

4. Quick Check:

   Missing return in arrow function with braces [OK]

Hint: Arrow with braces needs explicit return [OK]

Common Mistakes:

• Forgetting return inside braces
• Confusing selectors with actions
• Using wrong parameter names

5. You want to create a memoized selector using reselect to get the count of completed todos from state. Which code correctly implements this?

hard

A. import { createSelector } from 'redux';
const selectCompletedCount = createSelector(state => state.todos, todos => todos.length);

B. const selectCompletedCount = state => state.todos.filter(todo => todo.completed).length;

C. import { createSelector } from 'reselect';
const selectTodos = state => state.todos;
const selectCompletedCount = createSelector(
selectTodos,
todos => todos.filter(todo => todo.completed).length
);

D. const selectCompletedCount = createSelector(state => state.todos, todos => todos.completed.length);

Solution

1. Step 1: Use correct import and createSelector

   The createSelector function is imported from 'reselect' and used properly.

2. Step 2: Define input selector and output function

   selectTodos gets todos array; output function filters completed and counts them.

3. Step 3: Check other options for errors

   The plain selector const selectCompletedCount = state => state.todos.filter(todo => todo.completed).length is not memoized; importing createSelector from 'redux' is wrong; todos => todos.completed.length accesses property incorrectly.

4. Final Answer:

   import { createSelector } from 'reselect'; const selectTodos = state => state.todos; const selectCompletedCount = createSelector(selectTodos, todos => todos.filter(todo => todo.completed).length); -> Option C

5. Quick Check:

   Use reselect createSelector with input and output functions [OK]

Hint: Use createSelector from 'reselect' with input and output functions [OK]

Common Mistakes:

• Importing createSelector from wrong package
• Not memoizing selector
• Incorrectly accessing properties in output function