Redux Saga Explained: The redux-saga Tutorial
HTML-код
- Опубликовано: 7 сен 2024
- Redux Saga allows for asynchronous behavior and so much more. We will wire up redux-saga and use it to manage the state in our app both synchronously and asynchronously. We will also look at features that make redux saga a truly different type of middleware. Redux saga takes advantage of generators, which we will also cover in this tutorial!
REDUX SAGA IS A MIDDLEWARE. YOU MUST LEARN REDUX FIRST:
LEARN REDUX HERE: • Redux and React for Be...
Redux DevTools Extension: chrome.google....
*************
Starter files are in the repository
github: github.com/asa...
* open the STARTER FILES folder
* use the redux-saga folder to code along
*************
Previous Lesson: • Redux Thunk in React: ...
Hands down the best tutorial to learn redux-saga. Thanks!
Glad it helped!
It just took 50 mins for you to help us understand redux-saga. Now I can easily work with saga ..Great job. Keep it going :)
This is the holy grail for understanding redux-sanga. cheers!
Absolutely the best redux-saga video out there and I should know, I have seen them all
Valuable tutorial! ⭐
Thank you
5 minutes in and Im hooked! This is the best tutorial and thank you for creating this! Hoping for more content soon!
Thank you for the great and enriching tutorial...
If you'll ever have the motivation to upload another part for this topic,
I wish it will include an even deeper dive, with other effects, and the concept of "Channel" in Redux Saga.
But considering your teaching skills, any tutorial will be welcome..
Thanks watching! I'll look into Channel
This is so good. It should be there on recommendations page in the Redux Saga site.
very clear workflow explanation about the each roles in react ecosystem before saga and after saga, thank you very much!
good job . really great i was looking a course like this for a while .this is the best of all i could find. thank you
here like we learn this things on udemy or on somewhere its to much professional as well as simple thankyou sir for making this video
Thanks for the awesome tutorial! You make Redux-Saga look very easy.
Thanks a lot for the tutorial, it helped me a lot. Everything was so clear and very well explained. Great job Papa, appreciate it !
Glad it helped!
Everything in one place💕. Great job...
great tutorial, easy to understand, im waiting for your another tutorial
Thank you for the tutorial..
I'm glad it helped!
I love u for this!
I love you too Cosiocosh! Glad it helped
Awesome tutorial ++++++++++++++++++++++
Best
This is literally the best
This is a great tutorial for redux saga but if it was a real life application, we would just use plain actions and reducers for the cart since we don’t really need to handle any side effects (calling external api, etc) right?
Thanks Sir!
I seriously think actions should've been called as {name: 'ADD_TO_CART', data: item} instead of {type: 'ADD_TO_CART', payload: item} :/. It's like instead of saying my name is Aditya, I would say my type is Aditya as compared to people of type John and type Rob. It's not like there are groupings or subdivisions of ADD_TO_CART, this is a red ADD_TO_CART vs a green ADD_TO_CART; it's just a name for the action.
The redux documents use the key “payload” rather than the key “data”. They also use “type” rather than “name”. There is no difference, and you can use any key you would like.
But, I suggest you use the naming convention suggested in the docs if you will be working with a team of developers.
You’ll find this in the following document under the header “Redux Terminology”.
redux.js.org/tutorials/fundamentals/part-2-concepts-data-flow
@@PapaSanto I know Im just saying redux has named it badly; the difference is bad usage of English; sorry to say, but a lot of devs have poor English. From a dev perspective, name and data are easier to type, since there is so much boilerplate typing of these keywords in this. Bad conventions should be refactored, not accepted.
@@PapaSanto Listen to yourself speak at 1:21 in the video, "Sagas are catching things by their 'type name'". Had it been named correctly, you would've just said "Sagas catch actions by name."
I don't understand how come a function in watcherSaga with two yield statements ran on its own without us doing that function().next() thing?
When yielding in a generator like that, we are just asking the function to await a response before moving to the command
perfect!
Would have been the best but no one knows what's in your reducer because you didn't show what is there in the full tutorial
I did link you the code in your most recent comment. Here’s a link to the playlist incase you’d like to see the code written and explained:
ruclips.net/p/PL_kocBMOO_TymuwYrOA-Wj2jyp9l9agvb
Hope it helps
please upload the redux saga files
redux saga code files is not in git repo. Can you add them into git repo.
Hi Truelet. The redux saga starter files should be in the folder “STARTERS” in the git repo that is linked. Let me know if that helps
@@PapaSanto Yes, I have clone the repo but the complete redux-saga code and files unavailable in it. check once at your end. like sagas folder not exists.
@@truelet8219 yep, there is no sagas folder in it
How are you able to do over 50mins tutorials teaching people how to use redux, no one saw how you dispatched your actions nor how your reducer actually looks. Not cool, I just wasted my time here.
A link to the code is in the description. It is shown throughout the series that this video is part of.
If you’d like to see the code, you can do so here:
*************
Starter files are in the repository
github: github.com/asantono/StateInReact
* open the STARTER FILES folder
* use the redux-saga folder to code along
*************