Комментарии:
Good easy explaining!
ОтветитьClean and neatly explained! Good Job :)
ОтветитьWhy did add dispatch as dependency? is it because it will keep on calling again and again on the same page and it will show or add new data to the page if api data has increased from earlier.?
ОтветитьIt's very usefull lesson! Thank you so mauch
Ответитьgreat video
ОтветитьI never saw a so complex and over engineered way to handle memory in a browser! Im assume if someone who think in this library as an improvement see & or * before a variable will call the police!
ОтветитьGreat video, thank you!
ОтветитьGreat video, thanks for explaining this simple yet we tend to make it complex topic!
ОтветитьNice video
ОтветитьYou made me my day, great man!
ОтветитьIts really helpful. Thank you.
ОтветитьBeautiful explanation. Thanks a lot!
ОтветитьThank you well explained, beginner friendly and up to date and relevant 2023 April very easy to follow :) Thank you @EdRoh
ОтветитьThank you for the great video
ОтветитьGreat video! Would have really been a cherry on top if we had explored the unit testing side of all this. Probably the real win out of all this
ОтветитьVery good video, excellent explaining. Thanks!!!
The only thing is that the API doesn't provide anymore the prop image. So for those who are having problems, don't put the <img> and it will work.
thank you so much for this informative and awesome video keep it up
Ответитьhi can you please tell if i can pass a callback in dispatch to get success right after calling so i can redirect to different page after dispatch like doing login
ОтветитьThank you guy!!!
ОтветитьThank you. simple & clear
ОтветитьThank you. so simple, so informative, without any water)
ОтветитьYou make it easy to understand 👍
ОтветитьThanks. if this was typescript it would be epic tho :)
Ответитьwhat theme are you using, awesome video btw
ОтветитьThank you
ОтветитьVery informative, well explained and straight to the point. Wish I had seen this first, before delving into the docs. Keep it up!
ОтветитьThank you very much! It worked!
Ответитьhey edward, can you please explain why am i receiving error as 'catState is not defined' at line no 23 in catState.js file?
ОтветитьPlease help me: my catSaga and catState files are contains errors, because i'm using TypeScript. How can I modify those files to working in TypeScript?
ОтветитьGreat explanation. I like the nice and slow way you explain things. Thanks
Ответитьhow do pass any payload, to make post request using state from the component/ slice, inside the saga's worker function?
ОтветитьGreat , But for get the login details what will we do First we save the state and then call saga , like a function save the username password and then the saga is called ? or anything
ОтветитьWhere to perform create store logic if i am setting this in Next App
Ответитьamazing explanation, thank you
Ответитьthank you so much !!!
ОтветитьThank you for very nice explain!
ОтветитьDoesn't make any sense but interesting
Ответитьwhat if we have many saga?
do we have to combine them by using all effects like we do in typical saga?
It’s still have lots of code . If I use SWR or React query instead of using redux , is there will be any trouble?
Ответитьplease help me out here..
I've done the exact steps to integrate redux saga in my react project which was already using redux toolkit and while running my react project later my proj is not loading fully and I'm getting this error on my command prompt later
FATAL ERROR: Committing semi space failed. Allocation failed - Javascript heap out of memory
( I've tried using --max_old_space_size=4096 in my start script but nothing changes )
Please do it with TypeScript
ОтветитьThis is good. But what's wrong with the old approach where we have 3 directories store, actions and reducers?
Ответитьvery good tutorial. thank you!
ОтветитьAmazing ++++++++++++++++++++++++++++++
ОтветитьThis video was a lifesaver!
ОтветитьThis is great explanation. !!
ОтветитьGreat teaching, thanks
Ответитьgetting this error please help
"Uncaught Error: The slice reducer for key "cats" returned undefined during initialization. If the state passed to the reducer is undefined, you must explicitly return the initial state. The initial state may not be undefined. If you don't want to set a value for this reducer, you can use null instead of undefined.
"