Using State

Explore how Redux Thunk allows accessing the current state within action creators to conditionally dispatch actions. Learn to prevent duplicate recipe titles by checking state before dispatching, improving validation and keeping reducers simple.

We'll cover the following...

Another feature we gain by using redux-thunk is access to the state when processing the action. This allows us to dispatch or suppress actions according to the current application state. For example, we can prevent actions from trying to add recipes with duplicate titles:

const addRecipe = (title)

...

1.Introduction to Redux

2.Basic Redux Implementation

3.Cloning a Redux Boilerplate

4.Complete Redux Project

5.Creating a Store

6.Decorating the Store

7.Actions and Action Creators

8.Redux Thunk

9.Redux-Actions Library

10.Reducers

11.Avoiding Mutations

12.Introduction to Middleware

13.Your First Middleware

14.Middleware

15.State Management

16.Keeping a Normalized State

17.Persistence State

18.Real-World State

19.Server Communication

20.Moving Code from Action Creators

21.Error Handling

22.Server Communication II

23.Transforming Data

24.Chaining Requests

25.Managing Side Effects

26.Messaging Patterns

27.WebSockets

28.WebSocket Authentication

29.Testing

30.Testing Action Creators

31.Async Action Creators

32.Testing Reducers

33.Testing Middleware

34.Testing Async Middleware

35.Integration Tests

36.Evolution Of Redux

Assessment

Using State