Learn how to keep code maintainable and self-documenting by extracting action creators from the components.
Thx for the great tutorial series! Was educational w/o being overwhelming - Russian accent was cool to listen to as well.
Awesome series, thanks for taking the time to make it!
Wow. Incredible. THANK YOU!
Very fast paced videos. I really like seeing Dan write the code for some of the objects that are in the Redux eco-system.
For those looking for a project that utilizes all these concepts in a more complex example then the ToDo, you might want to look at my Snowflake project: https://github.com/bartonhammond/snowflake - It's more complex then a Todo but not so much that you can't wrap your head around it.
Just awesome, Dan! Thank you.
This was a wonderful and very instructive series. I really liked the approach where you implement stores and reducers via plain JS so we can see what's going on under the hood. Such simple, yet so powerful concepts. Hope you make more videos/series on React/Redux. Cheers.
Fantastic series. I now feel I'm not only a better Redux developer, but also a better React developer.
I had no idea why I'd want to use Redux when I started this course. This course really made it easy to understand the how & why of redux. Thanks Dan!
Thanks Dan and Egghead! This course was FANTASTIC!
Dan has an incredibly relaxing voice, and I noticed that he made very few, possibly NO errors at all while typing. Kind of amazing!
Thanks for this excellent tutorial. Dan is amazing developer or creator.
That was very helpful! Thank you very much!
Well done, learned a lot. Might be useful to add one more; refactoring the whole thing to separate files and recommended project/folder structure?
Check out Stephen Grider's starter https://github.com/StephenGrider/ReduxSimpleStarter . He also has examples for his Udemy course (which I took) at https://github.com/StephenGrider/ReduxCasts
Thanks Dan for the excellent walk through Redux. This helps me understand the flow of data and how to think of the application.
Series was great, thanks for making it! Feedbacks:
renderwas a good idea (these frameworks are new to me so there's a lot I don't understand), only to find out that in fact that isn't a good idea & you fix it later. Big red "We're going to fix this!" note on those would help me sort out what's confusing cuz it's new from what's confusing cuz it is in fact wrong.
Would be helpful if you highlighted places where you're doing it "wrong" but planning to rewrite it later. I struggled to understand how calling getState from render was a good idea
Good feedback, thanks!
Would love to see one or two short vids at the end breaking the application code out into a typical react/redux structure
I don’t have any specific file structure to suggest because I think it really depends on the app and the team, and people will repeat whatever I say even if it’s bad. So I’d rather not have any opinion at all about this.
Thanks for this course!
Very helpful tutorial series. I'm happy that you took the time to explain it at a slow pace, and summarize what happened in each lesson to really make people understand well. Thank you, I look forward to more!
Thanks for the excellent series, really appreciate it .
Great stuff, thanks Dan.
Could you add a video explaining how to integrate data from service and having an store that handles CRUD?
About error handling thought redux... What is the best approach to deal with errors? Like async errors. Is a global or a scope/component handler?
It was great Dan, Thanks a lot for this, I can't even type this message without using the backspace and I see you wrote the whole application without using the backspace even once. Pace was perfect and best part was how you wrote a native app and then improvised it.
But one thing i am not clear with is, you said not use context as it has changed earlier and will again. Then what is the best way to pass data ?
This course was awesome. Lots learned, lots or re-watching to really digest it and now a lifetime of application to master :D
Great lessons. Thank you very much. Priceless!!
Great Lessons on Redux.
Question: wouldn't the nextTodoId be in store (instead of the actionCreator) and updated by reducer ADD_TODO after the new entry is pushed to the array? So the store changes the todo array and increments the nextTodoId on add action. It's deterministic if the nextTodoId is part of the state, no?
This series has been the best tech learning experience ever, I feel others should also learn from the approach used to explain concepts. Thanks.
This was a terrible series. Why dump everything into a single file and there is way too much refactoring and unnecessary over-complication.
If you left feeling a little overwhelmed and confused try this tutorial:
Much better explained.
Great course! Dan, thank you!
I wish you would have added another episode where you went over everything again and how things connect. Also a video on separating this one file into multiple files would be helpful as well. Learned a lot
bad coding style to use the same name for several things, with only a difference in case or adding an 's', example AddTodo => addTodo Todo => todos ......This is a very bad style, and shouldn't be used even for demos, remember the next guy looking at your code will have trouble remembering the difference between the names.
Thank you, Dan. What a great course!. I love how you explain what happens under the hood of Store, CombineReducers and Provider Component.
Good stuff. Well explained. Thanks Dan.