2022-03-18
1911
#redux
Esteban Herrera
518
Mar 18, 2022 ⋅ 6 min read

Understanding Redux Saga: From action creators to sagas

Esteban Herrera Family man. Java and JavaScript developer. Swift and VR/AR hobbyist. Like books, movies, and still trying many things. Find me at eherrera.net

Recent posts:

A crash course in Next.js middleware

A crash course in Next.js middleware

Learn the ins and outs of Next.js middleware, which allows you to perform actions before a request is completed and modify the response accordingly.

Temitope Oyedele
May 23, 2025 ⋅ 9 min read
How AI Is Changing Debugging With Google Gemini

How AI is changing debugging with Google Gemini

The Google Gemini AI model has integrated AI-powered features to improve the debugging experience in web development.

Emmanuel John
May 23, 2025 ⋅ 5 min read
10 Node.js 24 features you're probably not using

10 Node.js 24 features you’re probably not using

The Node.js 24 release included significant updates. Explore 10 features you might not be using yet — but absolutely should be.

Emmanuel John
May 22, 2025 ⋅ 8 min read
six CSS animation libraries to bring your project to life in 2025

6 CSS animation libraries to bring your project to life in 2025

Explore six of the best, easiest, most configurable, and convenient CSS animation libraries available in 2025.

Murat Yüksel
May 22, 2025 ⋅ 8 min read
View all posts

5 Replies to "Understanding Redux Saga: From action creators to sagas"

  1. “A middleware is a piece of code that is executed after an action is dispatched but before reaching the reducer”.
    It’s the opposite – first reducer, then saga

  2. Hi,
    Not sure if I am missing something here, but with just one, simple call to API what is the point of using SAGA, instead of simple Thunk ?

Leave a Reply