Thus, all that said, redux-saga's power lies when your system is getting more complex and event-driven. Redux saga acts as a middleware that gives developers the scope to neatly separate any business logic, xhr Requests(Popularly known as Ajax), data manipulation or any other operation which may not.
REDUX SAGA GENERATOR
In redux saga we make all the functions as generator functions. what it will do it will take all the action type of GETPOSTS, and execute the postAsyncs function every time. A root Saga aggregates multiple Sagas to a single entry point for the sagaMiddleware to run. Redux Saga is a redux middleware, which means this thread can be started, paused and cancelled from the main application with normal redux actions, it has. Yield cancel(task) // cancel a task if syncing is stopped In the code above we have created a mySaga watcher function, and in that function basically, we are calling takeEvery side-effect of redux-saga. In a saga, fetch will look something like this: function* fetchItems(action) Ĭonst task = yield fork(doSync) // returns a task A saga is not dependent on the lifetime of a component. This way, it has clear separation of concerns that the middleware is going to handle the side effects and not the component.
REDUX SAGA UPDATE
Now what you are doing is handling the side effect in the component so the action youll dispatch will only update the store.
redux-saga executes our generator functions (sagas) containing the side-effects then handles the process of calling the next () on the generator object internally. Redux-saga is a middleware to act on an action before it reaches the reducer.īasically, all side effects will be handled in the middleware and gives you more control over the effects. In simpler words redux-saga is beneficial in the case where we need to achieve some async operation during a redux action. What redux-saga does is to run our sagas (generator functions) and provide methods for handling the side-effects and also interacting with the redux store.
0 kommentar(er)
