Why I like your video? You are not just telling what to do, but you are teaching how to read documentation too, that is most important steps to be a developer, watching you as how to use development is what i learnt.
I am starting a new react project from scratch and thank this series I will be using typescript with redux-toolkit with confidence. I used plain redux before and this looks so much cleaner and easy to follow. The way you teach is really great, thanks A LOT Jack!
Thinking about a short series around building an app with firestore and considering using redux toolkit for that. Interesting twist on the usual asynchronous stuff since it's a subscription model.
@@jherr I know Firestore has a realtime database. Oh, getting into that would be awesome especially with typescript. All the best. Looking forward to it.
Have a comment just because I enjoy your videos! I come from an Angular/Vue background and moved to react, and your state videos really helped getting an overview of what to use for a bigger project! Keep it up.
Its worth watching the video . Could you please make videos on standard practices while using reacttoolkit and unit testing using jest and react-testing library
I was trying for about 4 days to find good example of use typescript + redux toolkit and I was so lucky to come here :D Best tutorial ever, gr8 teacher, i hope you get 1 000 000 subs soon!! You deserve it :)
You manage to realize a concept demo redux,in ts under 15 mins in a concise and clear fashion. Given the other tuts do it in 40-70 mins or more I find this impressive af. One thing that I recommend. Do NOT allocate id based on array length. This will break as soon as you delete one. Just whip up a randId function instead.
Totally agree on the ID, that was just to keep it brief, but I should always avoid teaching anti-patterns in any case because people will clone that code and won't think about the obvious consequences.
@@darkmift I will try that out. Thanks! There are some little small mistakes in the videos that I'd like like fix. It's usually in the things I say, for example I called GitHub Copilot "GitHub CLI" a couple of times in a video recently. Sigh.
Great tutorial! But somehow, updating the state directly in the slice actions didn't work for me.. I had to return the new value in the actions in order to make it update the state..
Thanks for the great video. I have only used plain redux, and the redux toolkit does seem to provide some convenience features like writing separate reducer functions that update the state instead of having a single function with a big switch statement. But what I observe here is that these functions mutate the original state object instead of returning a new one with the updated state. Is this ok to do -- making deeply nested mutations in the state object in these reducer functions?
Oh yes, Redux has changed a bit... a few days ago this came up in my TH-cam feed: th-cam.com/video/9zySeP5vH9c/w-d-xo.html It's a pretty comprehensive video from Jason Lengstorf channel, with Mark Erikson, who seems to be in the Redux team, so it's all about 'modern' Redux in TS.
Hi, its really a nice video. Can you please make a video on creating test case for using redux-toolkit in React typescript with Jest and React testinglibrary. It will be great help then.
it is clear that you have a long experience and you are professional programmer, but not enough explanations, a little bit in hurry so it is hard to catch you without repeating the video, that depends on which level you are targeting, the problem not with understanding, the amount of new information needs to be connected together, maybe slowing down the playback speed would help. programming is not physics or mathematics depends only on the accumulation of knowledge and understanding (for instance this video mostly new),
It's really disappointing to see Redux gravitating to "mutating stuff in place". I know it uses Immer under the hood, but I'm baffled why they chose this approach for a library that got famous by introducing functional concepts to React (and other FE libraries/frameworks).
They are't really mutating in-place. They are mutating a copy. It's really just syntactic sugar that allows the function to concentrate on setting particular state values and now have to worry about saying; "copy the rest of the state, but alter these things" the code can just "alter these things".
@@jherr You're absolutely right. I was mainly commenting on the decision to use syntactic sugar in the first place. I personally find it misleading given the architecture design of Redux as now the implementation details are hidden, making it easier to form wrong assumptions on how reducers are working.
@@jherr Well, I guess things evolve, maybe I got used to the passing state around too much :) Thanks for the really great content btw, keep them coming 👍
@@akis854 IMHO, the future of state management is reactive state and I'll be talking about that next week. Vue 3's new model is reactive, RxJS is reactive, React hooks are reactive, Recoil/Jotai are reactive, newer frameworks like SolidJS and Svelte are reactive. It's pretty cool stuff, I'm excited to share it.
Why I like your video?
You are not just telling what to do, but you are teaching how to read documentation too, that is most important steps to be a developer, watching you as how to use development is what i learnt.
I am starting a new react project from scratch and thank this series I will be using typescript with redux-toolkit with confidence. I used plain redux before and this looks so much cleaner and easy to follow. The way you teach is really great, thanks A LOT Jack!
I have learned a lot about typescript and react in this series, I had not implemented the redux toolkit. Thanks Jack
This is so fun to watch easy to understand explaining in details. This has enhanced my understanding of redux
Very well explained. Really helped me with my typescript issues on Redux. Love it.
I've watched this entire series from the start. This is EXCELLENT stuff, Jack. Hopefully, you can explore Redux toolkit with typescript further.
Thinking about a short series around building an app with firestore and considering using redux toolkit for that. Interesting twist on the usual asynchronous stuff since it's a subscription model.
@@jherr I know Firestore has a realtime database. Oh, getting into that would be awesome especially with typescript.
All the best. Looking forward to it.
Thank's a lot
Have a comment just because I enjoy your videos! I come from an Angular/Vue background and moved to react, and your state videos really helped getting an overview of what to use for a bigger project! Keep it up.
Respect! These videos are the best free resources I've come across! It's just a huge bonus that they actually have great examples to cement them
Its worth watching the video . Could you please make videos on standard practices while using reacttoolkit and unit testing using jest and react-testing library
I was trying for about 4 days to find good example of use typescript + redux toolkit and I was so lucky to come here :D
Best tutorial ever, gr8 teacher, i hope you get 1 000 000 subs soon!! You deserve it :)
Great series and easy to follow! 👏
This really does simplify approaching Redux in TypeScript. Just need to read up on how you work with Async actions using Redux-Toolkit.
@Neil Rice Thank you!!!
I was just reading the Redux Toolkit docs.
Great work, many thanks Jack! (this comment is for you and for youtube algorithm)
Thanks a lot, this video clarify my path trough redux
Awesome Jack! Can you please make a followup to this that includes createAsyncThunk with ThunkAPI?
Love it! A suggestion for a future video is how to type custom Redux Toolkit middleware...
coolest course on the planet
This is great to start! Thanks a lot!
Nice video Jack! Thanks for sharing!
You manage to realize a concept demo redux,in ts under 15 mins in a concise and clear fashion.
Given the other tuts do it in 40-70 mins or more I find this impressive af.
One thing that I recommend.
Do NOT allocate id based on array length.
This will break as soon as you delete one.
Just whip up a randId function instead.
Totally agree on the ID, that was just to keep it brief, but I should always avoid teaching anti-patterns in any case because people will clone that code and won't think about the obvious consequences.
@@jherr you can always slap an edit subtitle on that bit.
But all in all its great content!
@@darkmift I will try that out. Thanks! There are some little small mistakes in the videos that I'd like like fix. It's usually in the things I say, for example I called GitHub Copilot "GitHub CLI" a couple of times in a video recently. Sigh.
@@jherr The last pancake is always better than the first 😃
Thank you so much, this tutorial was gold!
As always great content much appreciated.
Thank you for the great tutorial!.
I wish I was starting a new project to use this. It is kind of hard to introduce it in an existing project! It looks very handy!
Cool, I'll try to implement it on an Auth system! cheers!
Thank you very much, sir. you saved me
Great tutorial! What name for font that you use in vscode? Thankyou.
Loving this sooo much!
This is so awesome!
Great video - thankyou for putting the effort in
Thanks, very helpful video
Great video, thank you!
Great tutorial! But somehow, updating the state directly in the slice actions didn't work for me.. I had to return the new value in the actions in order to make it update the state..
Hmmm... That should work. You should check the docs and then if you can't get it to work then hit up their Discord.
Awesome content as usual!!
Thanks for the great video.
I have only used plain redux, and the redux toolkit does seem to provide some convenience features like writing separate reducer functions that update the state instead of having a single function with a big switch statement. But what I observe here is that these functions mutate the original state object instead of returning a new one with the updated state. Is this ok to do -- making deeply nested mutations in the state object in these reducer functions?
I think whatever is wrapping them is making a shallow copy of the state object and then you are mutating it. Same kinda thing with Immer.
RTK uses Immer under the hood
Oh yes, Redux has changed a bit... a few days ago this came up in my TH-cam feed: th-cam.com/video/9zySeP5vH9c/w-d-xo.html
It's a pretty comprehensive video from Jason Lengstorf channel, with Mark Erikson, who seems to be in the Redux team, so it's all about 'modern' Redux in TS.
great tutorial
Hi, its really a nice video. Can you please make a video on creating test case for using redux-toolkit in React typescript with Jest and React testinglibrary. It will be great help then.
awesome and simple
Awesome thanks
You don't need the spread as rtk uses immer inside createSlice
nice video bro.
Why do we have state.todos.todos structure. Initial state for todosSlice is todos: Todo[]. Where do I miss an embedded object?
Tks a lot!
Comment for the algorithm :D
Ty :)
Content is what I was looking to but you could have just slowed it down. Thanks
Comment for the algorithm
So smart
great
Good content, you should create courses on Udemy for million of students can learn React, Redux... knowledge from you.
Zustand or redux toolkit?
You get to judge tomorrow as Zustand is tomorrow's video.
Good
nope! Not getting this one. Not a fan of copy paste without knowing what is up and why
it is clear that you have a long experience and you are professional programmer, but not enough explanations, a little bit in hurry so it is hard to catch you without repeating the video, that depends on which level you are targeting, the problem not with understanding, the amount of new information needs to be connected together, maybe slowing down the playback speed would help.
programming is not physics or mathematics depends only on the accumulation of knowledge and understanding (for instance this video mostly new),
Agreed, I need to do a lot more in-depth redux toolkit video.
Thanks for your work!
sir.. you looks like donald trump.. sorry out of topic.. just wanna saya hehe
It's really disappointing to see Redux gravitating to "mutating stuff in place". I know it uses Immer under the hood, but I'm baffled why they chose this approach for a library that got famous by introducing functional concepts to React (and other FE libraries/frameworks).
They are't really mutating in-place. They are mutating a copy. It's really just syntactic sugar that allows the function to concentrate on setting particular state values and now have to worry about saying; "copy the rest of the state, but alter these things" the code can just "alter these things".
@@jherr You're absolutely right. I was mainly commenting on the decision to use syntactic sugar in the first place. I personally find it misleading given the architecture design of Redux as now the implementation details are hidden, making it easier to form wrong assumptions on how reducers are working.
@@akis854 Fair enough. And yeah, in a sense it's moving away from the Redux roots.
@@jherr Well, I guess things evolve, maybe I got used to the passing state around too much :)
Thanks for the really great content btw, keep them coming 👍
@@akis854 IMHO, the future of state management is reactive state and I'll be talking about that next week. Vue 3's new model is reactive, RxJS is reactive, React hooks are reactive, Recoil/Jotai are reactive, newer frameworks like SolidJS and Svelte are reactive. It's pretty cool stuff, I'm excited to share it.
thunks? 🥲
Right? Ugh. I feel like we are back in Win32.
@@jherr 😂I am making my first application with redux and typescript and it is very difficult for me, by the way it is win32?