❤best video, I wasted 2 days watching some dumb tutorial about redux-saga and never understood the flow. Now the flow of redux-action -> watcher saga -> handler function -> request function -> handler function -> yield put to reducers is clear. Thanks a ton, man!
Possibly one of the best explainers I've come across yet. This actually might help me solve a headache I was having with complex state management issues this week.
Thank you for everything. Nothing is being taken for granted, And I wish you'll keep uploading much much more content. With that being said, 28:36 - most of the time your explanations are clear, but.. What does it mean: "YOU CAN go ahead to add that to the useEffect" ? Or "YOU MUST"? 28:40 - "It is not going to make a difference because this dispatch is not going to change any time soon" - Mmm... What?! Is that a valid reason to add dependency? -What a vague explanation. AND WHEN it will change, it will get updated and trigger an infinite loop?? - no? why not? Other than that, another great tutorial.. (..although you were mentioned the word "Channel" in the cotext of Saga without going any further, and I hope the following videos will include this topic..)
This was great, I really enjoyed building the app to use the mock API. I find that understanding the material becomes so much easier if you code along or copy from the code sandbox into your own working code. Tracing the flow of execution from the initial action through the reducer/saga/handler/request helps make the concepts much clearer. Thank you!
Thank you soooooo much! You cleared my concept and now I'm longer afraid of the saga and also thanks for the DUCK pattern it made things a lot easier. Thanks again for saving my day.
I watched lot of videos to understand Redux saga concept but did not get it, your videos are excellent and I got clear understanding on this and also I like the way you explain
Please, just please, do not stop with these tutorials about React!!. As i said before, THIS IS PURE GOLD! Do you have any paid content so i can buy and support you ?
Thank you for the tutorials, I teach and I needed to make sure that I understood everything again before I taught it (I forget many things so I have to make sure I am up to it date) and this was the perfect refresher! I should just refer my students to this channel instead lol.
It pains me to tell you Anthony that the video was complicated. It felt like I am repeating steps. Its a contructive criticism, and I feel I need to learn more and come back to this video.
I really enjoyed your previous video (#12) on redux with duck pattern , however, it was more easier to understand react saga if you would have tried duck pattern with redux-saga too , I did not follow your pattern (splitting in many files), first I simply put whole things like handler , watcher everything into configurestore file and later moved into one file only , then it became much easier to me.
I'd suggest having different names for js files, like userRequest, userHandler. In a big project with a more complex file structure having files with the same name will get confusing fast.
I would really appreciate a video which shows how saga simplifies things over axios or other methods. I take in faith that there is some point, but all I can see at present are overcomplications and redundancies. Redux itself serves a valuable purpose, but similarly I still don't understand the reasons for what seems to me an overcomplicated structure.
you all prolly dont care at all but does any of you know a tool to log back into an Instagram account? I stupidly forgot the login password. I love any assistance you can offer me.
@Kalel Jon I really appreciate your reply. I found the site on google and I'm in the hacking process atm. Looks like it's gonna take a while so I will get back to you later with my results.
So to break it down Saga is a middleware that handles async data before storing state into the redux store. I'm still trying to get my head around reducers. I'm guessing I should jump to #16 as it includes the latest Redux toolkit. I'm determined to learn this even on Christmas Day!! Edit: this tutorial is outdated. Thunk is included with RTK. Still following along though and see if I can add all this into RTK instead
thanks for this explanation. i have only one question in the generator function after the first yield finished who made .next() to your function to resum the work ? because there an other yield for put. thanks so mutch
Hello, Anthony. Thanks so much for this tutorial and I have a question. When I'm incrementing / decrementing it's logging in the console that user object from the API call that we've made. Can you tell me why?
Hi Anthony very clear. I got a question for you, it looks very powerful but also more complicated, I understand that Redux simplifies the state management, but could we fetch data directly from the UI Component instead of adding Redux Saga? if so, What´s the trade off?
Yes! Some of my videos on useEffect covers how to do that. The biggest drawback is in more complex application with data being shared through multiple components, it becomes hard to manage how they get stored in redux without redux saga. Also Redux Saga can handle many things like snackbars and dealing with 400 errors as well as successful calls in general.
Hey Antony, I’m using redux tool kit, and as you already know it uses thunk. I know you advocate saga, but can you tell me what sagas brings more to the table? Or will I be good to go with think.
Pls explain selector... Also pls make some task oriented tutorial.. so that everyone ll like to subscribe and u ll get more views for sure.. bcoz it helps a lot to employees to work on user stories.. no one channel is doing like this.. For ex- there is api based on node js. Companies ll tell to work on saga, selector, think, context api or whatever to complete the requirements..
In the 31:30 mark you mention about creating a separate threads. I assume that this in reference to the browser creating a new thread for the ajax request and not that redux saga will actually create a new thread (ie use web workers)? I thought that multi threading is not something you can code in a browser unless you use web workers.
Hi buddy, please don't take my comment as a negative comment, I like your videos and you really simplify a lot of things, but i did the same same thing exactly using CONTEXT API in just few lines of code! why we really need to use Redux-Saga ? your answer will be so helpful to highlight the importance or the best use cases for each tool. I'm not against Redux, but i'm against the unneeded complicity, did you get my point ?
Great question! The context api is a very useful tool, and I would suggest using it whenever possible! Redux + Redux saga is more meant for bigger applications, ones where you're making over 20 API calls to different endpoints, and you're keeping a ton of data in different reducers. Overall, it's an architecture meant for bigger enterprise applications, where react's context gets too cluttered and disorganized to handle.
tbh... all these redux solutions (saga, thunk, observable) were very useful during the earlier days before async/await and React Hook were introduced. Then things become simpler later on after more and more hooks introduced. And the introduction of ContextAPI give us another choice of managing state in your application, which you can organise your code base in a way cleaner (less boilerplate code), though that doesn't mean it will replace redux.
great video BUT for learning purposes that would be much better if you had NOT put every file in separate folders and kinda do it the same way that saga does it in its document, this way when new students can see every related things all in one place they can absorb it faster, and THEN, of course, you can add another 5-10 minutes at the end and show how it could be done by separating folders and now students can learn the folder pattern as well,
One of the best guide to Redux-Saga.
Dude, I just want to say that you are an incredibly talented instructor.
❤best video, I wasted 2 days watching some dumb tutorial about redux-saga and never understood the flow. Now the flow of redux-action -> watcher saga -> handler function -> request function -> handler function -> yield put to reducers is clear. Thanks a ton, man!
Hitting an API and walking through the redux saga flow was exactly what I needed, thank you for making this video!
Underrated. Please don't stop, this is brilliant
Possibly one of the best explainers I've come across yet. This actually might help me solve a headache I was having with complex state management issues this week.
your english your way of explaining all makes it so simple to understand
This one was tough but it's just because I'm bad. Eventually got the idea after rewinding many times. Cheers Anthony
In my case, you are my best teacher ever. I liked your explanation and your videos about react and redux things. Thanks a lot
I guess this is the most comprehensible redux-saga explanation I've ever seen, thanks man.
This tutorial of Redux Saga was what I needed! So clear explanation of the flow and the concepts. Thanks Man, Keep it Up!
correct
Thank you for everything.
Nothing is being taken for granted,
And I wish you'll keep uploading much much more content.
With that being said,
28:36 - most of the time your explanations are clear, but..
What does it mean: "YOU CAN go ahead to add that to the useEffect" ?
Or "YOU MUST"?
28:40 - "It is not going to make a difference because this dispatch is not going to change any time soon"
- Mmm... What?! Is that a valid reason to add dependency? -What a vague explanation.
AND WHEN it will change, it will get updated and trigger an infinite loop?? - no? why not?
Other than that, another great tutorial..
(..although you were mentioned the word "Channel" in the cotext of Saga without going any further, and I hope the following videos will include this topic..)
Perfect explanation of redux-saga concept with proper example.
Thank you so much @ReactJS Hub👍
one of the best video now i found on saga on youtube
This was great, I really enjoyed building the app to use the mock API. I find that understanding the material becomes so much easier if you code along or copy from the code sandbox into your own working code. Tracing the flow of execution from the initial action through the reducer/saga/handler/request helps make the concepts much clearer. Thank you!
Everyone should watch this guy's videos! Its so easy to understand for beginners
Your explanation of how redux-saga is crystal clear. Thank you!
Anthony can not thank you enough for making everything so easy to follow and apply, thanks man.
Thank you, this is the best saga video anywhere.
Just thank you for this value and this clear explanation of what Saga is and how we can set it up !
Top Marks !!!, best sagas video anywhere online IMO !!!
Thank you soooooo much! You cleared my concept and now I'm longer afraid of the saga and also thanks for the DUCK pattern it made things a lot easier. Thanks again for saving my day.
Certainly the very best video I've ever seen about redux stuff. Thank you very much :)
I watched lot of videos to understand Redux saga concept but did not get it, your videos are excellent and I got clear understanding on this and also I like the way you explain
Please, just please, do not stop with these tutorials about React!!. As i said before, THIS IS PURE GOLD!
Do you have any paid content so i can buy and support you ?
Thank you so much! Glad you like the tutorials :) I don't have any paid content haha! Just a like and a comment is good enough for me
@@AnthonySistilli You should have like a voluntary contribution section
If I could give Anthony a standing ovation, I would!
could you?
i love whole playlist but this become really complicated here, went over my head
Glad i'm not the only one...this video was super confusing to me but the other videos made sense to me
Thank you for the tutorials, I teach and I needed to make sure that I understood everything again before I taught it (I forget many things so I have to make sure I am up to it date) and this was the perfect refresher! I should just refer my students to this channel instead lol.
You are love understand saga for the first time ♥️
good explanation of react redux saga
And in the end your way of explaining the complete code in seconds was simply amazing
Thank you. Very beginner friendly and clear explanation.
That is actually all I need to know about saga. that was great, you are the best!
This is a great video Anthony. It's a few years old but it's still helpful.
this is exactly what I needed you are legend my guy!!!!!
It pains me to tell you Anthony that the video was complicated. It felt like I am repeating steps. Its a contructive criticism, and I feel I need to learn more and come back to this video.
Super helpful! Great explanations on the takeEvery, takeLatest etc...Thanks!
I really enjoyed your previous video (#12) on redux with duck pattern , however, it was more easier to understand react saga if you would have tried duck pattern with redux-saga too , I did not follow your pattern (splitting in many files), first I simply put whole things like handler , watcher everything into configurestore file and later moved into one file only , then it became much easier to me.
Thank you so much
Anthony Sistilli,This tutorial made my day.
I'd suggest having different names for js files, like userRequest, userHandler. In a big project with a more complex file structure having files with the same name will get confusing fast.
This was a really good explanation. Thank you for the informations
I would really appreciate a video which shows how saga simplifies things over axios or other methods. I take in faith that there is some point, but all I can see at present are overcomplications and redundancies. Redux itself serves a valuable purpose, but similarly I still don't understand the reasons for what seems to me an overcomplicated structure.
It's always your choice as a developer, how to write your code.
you all prolly dont care at all but does any of you know a tool to log back into an Instagram account?
I stupidly forgot the login password. I love any assistance you can offer me.
@Brodie Jake instablaster =)
@Kalel Jon I really appreciate your reply. I found the site on google and I'm in the hacking process atm.
Looks like it's gonna take a while so I will get back to you later with my results.
@Kalel Jon It worked and I actually got access to my account again. I'm so happy!
Thanks so much you really help me out!
So to break it down Saga is a middleware that handles async data before storing state into the redux store. I'm still trying to get my head around reducers. I'm guessing I should jump to #16 as it includes the latest Redux toolkit. I'm determined to learn this even on Christmas Day!! Edit: this tutorial is outdated. Thunk is included with RTK. Still following along though and see if I can add all this into RTK instead
Thanks for this A+ Tutorial on Redux Saga
I really enjoyed watching this video, thanks
Really good job, Anthony! Thanks!
This was great and helpful 😍, Keep going bro
Thanks
Another amazing video. Thank you Anthony and keep up the good work!!!
exactly what I needed. Thank you so much
This channel helped me a lot solving problems which were in my mind. Thank you so much bro
Wow!. You explained it really well, Thanks.
damn just finished the video and now i have to wait for next week again...
nice informative video man I only understood it from your video so far ^^
big thanks brother...very nice tutorial...please make a video on mobx react with typescript
Thanks a lot , the video was really great and your explanation is so clear.
Anthony can you help us to create Material-UI Open Drawer Underneath AppBar?
thanks for this explanation. i have only one question in the generator function after the first yield finished who made .next() to your function to resum the work ? because there an other yield for put. thanks so mutch
amazing. You have a gift for explaining stuff. Thank you for this
Hello Anthony! This video helped me a lot, thank you! ☺️
This is my first time hearing about redux saga and it does sound a bit complicated. Hoping I'll understand it better in time.
Great video Anthony. It was really helpful. Thanks a lot.
@Anthony what theme you’re using , great font
Man, I have watched a few other videos on sagas and I was dumber and dumber after each one. You nailed it though, great explaining skills, kudos!
Thank you, explained very well.
Hello, Anthony. Thanks so much for this tutorial and I have a question. When I'm incrementing / decrementing it's logging in the console that user object from the API call that we've made. Can you tell me why?
Hi Anthony very clear.
I got a question for you, it looks very powerful but also more complicated, I understand that Redux simplifies the state management, but could we fetch data directly from the UI Component instead of adding Redux Saga?
if so, What´s the trade off?
Yes! Some of my videos on useEffect covers how to do that. The biggest drawback is in more complex application with data being shared through multiple components, it becomes hard to manage how they get stored in redux without redux saga. Also Redux Saga can handle many things like snackbars and dealing with 400 errors as well as successful calls in general.
@@AnthonySistilli OK, got it. Probably when working on more complex projects, makes sense the overhead. Thank you very much.
Great explanations, thank you sir
Hey Antony, I’m using redux tool kit, and as you already know it uses thunk. I know you advocate saga, but can you tell me what sagas brings more to the table? Or will I be good to go with think.
And of course I miss your course, today is learning day, Monday.
Pls explain selector... Also pls make some task oriented tutorial.. so that everyone ll like to subscribe and u ll get more views for sure.. bcoz it helps a lot to employees to work on user stories.. no one channel is doing like this..
For ex- there is api based on node js. Companies ll tell to work on saga, selector, think, context api or whatever to complete the requirements..
Anthony your tutorials are great. Very helpful. Favor to ask though: can you do some videos on react testing? Say with mocha or jest.
thank you bro! your explanation is enlighten me
thank you so much for this amazing tutorial
Good job Anthony !!
Thank you! You actually helped me a lot
Amazing vid! Thanks so much!
great course, thanks man!
Thanks for the video mate 😊
Thank you so much for the tutorial.
Thank you, The video is very helpful
In the 31:30 mark you mention about creating a separate threads. I assume that this in reference to the browser creating a new thread for the ajax request and not that redux saga will actually create a new thread (ie use web workers)? I thought that multi threading is not something you can code in a browser unless you use web workers.
Dumbt it down pls
Thank you for the video !! It would be helpful if you can add some kind of animation to explain the redux saga flow...
Nice explanation in the video
Sir pls increase the frequency of the video
Hi buddy,
please don't take my comment as a negative comment, I like your videos and you really simplify a lot of things, but i did the same same thing exactly using CONTEXT API in just few lines of code! why we really need to use Redux-Saga ?
your answer will be so helpful to highlight the importance or the best use cases for each tool.
I'm not against Redux, but i'm against the unneeded complicity, did you get my point ?
Thanks buddy , but i'm Still waiting your answer about my question , your opinion is so important for me :)
Great question! The context api is a very useful tool, and I would suggest using it whenever possible!
Redux + Redux saga is more meant for bigger applications, ones where you're making over 20 API calls to different endpoints, and you're keeping a ton of data in different reducers. Overall, it's an architecture meant for bigger enterprise applications, where react's context gets too cluttered and disorganized to handle.
@@AnthonySistilli Thanks Buddy, i heard also that Context API effects the performance, is this true ?
tbh... all these redux solutions (saga, thunk, observable) were very useful during the earlier days before async/await and React Hook were introduced. Then things become simpler later on after more and more hooks introduced. And the introduction of ContextAPI give us another choice of managing state in your application, which you can organise your code base in a way cleaner (less boilerplate code), though that doesn't mean it will replace redux.
Great tutorial, thanks!
great video
BUT for learning purposes that would be much better if you had NOT put every file in separate folders and kinda do it the same way that saga does it in its document, this way when new students can see every related things all in one place they can absorb it faster, and THEN, of course, you can add another 5-10 minutes at the end and show how it could be done by separating folders and now students can learn the folder pattern as well,
Too Good thanks Anthony Sistilli
It would be better if you can make a video explaining redux-toolkit.js with redux saga/ thunk middlewares.
Thanks for your contribution.
Super good buddy! Thank yOU !!!
when can we use fetchEvery?
Great explanation
best explanation
This video is like cyclone hit on my head.
Great video, thank you so much!
Guys content creation is tough. I suggest do projects with concept thought.. week will fly just like that
thanks for learninig redux saga
Great video thanks.
Great Video :)
Thanks Anthony!!!
Great bro! Thanks