So the benefits over thunks is that it isolates side-effects away from actions so your actions become easier to test? Downside is you need to get that generator functions concept.
Also synchronous looking code, which is also possible in thunk using async-await. I think no matter from where I learn about saga. I willa always have doubts regarding it
Thanks a lot for this explanation. I have only one question in generator function when the first yield finish who call the second yield put ? i think we must have .next() some where
In effect, Sagas runs on its own thread, which keeps the two blocks of code from interfering with each other. Image you have a database intervention, using sagas you will make this in the background, thus you avoid blocking the main thread.
Agree with the guys below me, helped me too, I just hope I will be able to implement it into a React Native project now :D I couldn't find any docs on that, unfortunately
Question for anyone able to answer: Can you use Saga (just Saga) with React's Context API? (the Context API is another way to manage state instead of using Redux)
saga is just a middleware, if you use redux then you can envoke all middlewares by official library or community based library (like thunk, saga) or your own library, it is just an observable pattern to watch some event to happend and according to that fire some more events that can be async, so, Let's talk about context api, first it does not support adding middleware yet, but you still can create your custom hooks like useSaga, and then in that hook, you can pass some events types references to observe. it will kinda work same but it too much manual work :)
Depends upon the requirements ,do not jump library to library just a suggestion, prefer vanilla jacascript if you will. If you require low frequency updates definately you should use context api ,it's lighter and simple to use, but if you require long running asynchronous requests and better understanding of these requests try to explore both thunk or saga ,they share the same goal but slight change in middleware consumption.
![BOWKYLION - วิงวอน (ex-change) [Official MV]](http://i.ytimg.com/vi/cLdnZWDaO-w/mqdefault.jpg)
Much better, useful and concise than redux-saga documentation. Thanks a lot.
So the benefits over thunks is that it isolates side-effects away from actions so your actions become easier to test? Downside is you need to get that generator functions concept.
Also synchronous looking code, which is also possible in thunk using async-await. I think no matter from where I learn about saga. I willa always have doubts regarding it
can you please share the deck used in this video, this was a very clean explanation.
This is a great explanation of how Redux-Saga works. Great presentation.
No filler
To the point and no bs! Great presentation!
One of the best explanations of saga, Thank you!!!
Great presentation. To the point and very very clear. Thank you.
Short and sweet presentation. Thanks
one of the clearest explanation ever. thank you so much!
The best resource on redux-saga so far
Crazy enough.... but this still is the best explanation of sagas ... and btw generators also .. yield* with the asterisk I even never saw in practice
thank you, your presentation really makes my day 😀
best explanation on redux-saga
Very nice explanation without not needed complexity. Thanks
Thanks a lot for this explanation. I have only one question in generator function when the first yield finish who call the second yield put ? i think we must have .next() some where
great explanation. thank you
Good presentation. I am not completely sold though. Most of the points he makes can be covered by using async/await in thunks.
Does saga run on separate thread (web worker) or the same main thread?
In effect, Sagas runs on its own thread, which keeps the two blocks of code from interfering with each other.
Image you have a database intervention, using sagas you will make this in the background, thus you avoid blocking the main thread.
Why not to use async/await? These generators in saga makes code unreadable
Agree with the guys below me, helped me too, I just hope I will be able to implement it into a React Native project now :D I couldn't find any docs on that, unfortunately
This is a fantastic resource. Thank you!!!
This really helps.Thank you.
Great explanation. Thanks a lot!!
Excellent!
Can someone please tell me how yield select and yield fork works?? +FullStack Academy
Question for anyone able to answer: Can you use Saga (just Saga) with React's Context API? (the Context API is another way to manage state instead of using Redux)
saga is just a middleware, if you use redux then you can envoke all middlewares by official library or community based library (like thunk, saga) or your own library, it is just an observable pattern to watch some event to happend and according to that fire some more events that can be async, so, Let's talk about context api, first it does not support adding middleware yet, but you still can create your custom hooks like useSaga, and then in that hook, you can pass some events types references to observe. it will kinda work same but it too much manual work :)
@@creative-commons-videos Great, I won't be using Saga. I agree, sounds like so much work. Thank you so much!
Depends upon the requirements ,do not jump library to library just a suggestion, prefer vanilla jacascript if you will. If you require low frequency updates definately you should use context api ,it's lighter and simple to use, but if you require long running asynchronous requests and better understanding of these requests try to explore both thunk or saga ,they share the same goal but slight change in middleware consumption.
the video referenced in the last slide is th-cam.com/video/9UZla3uIo3A/w-d-xo.html
Cool!
good explanation
thanks
Now add types...
Thanks
👌
So happy we can speed up the playback speed to 1.5x
2x is better
Use a mic in your collar ... the volume up and down is extremely disturbing ...
yeet
Clearly knows his sage, but maybe want to liven up a bit. Also watch your video, mic issues!