I really don't think it matters what point you decide to transition from vanilla redux to redux-toolkit. Of course it's easiest to initially write all your code using the toolkit if you are planning on implementing later, just to save time and some headaches.
BUT, I also think that by writing you code in vanilla redux first, and then switching over can be very beneficial if you are newer to the react/redux realm. I've found there are ton of different ways to utilize Redux toolkit and you will come across tutorials and documentations showing it's versatility. Understanding your application, your reducers, actions, etc. will help you pick apart other code you may be learning from, so you're not just pattern following without understanding what's really going on. If you're really nervous about breaking your code, clone your repo, and try it out there first!
tldr, go for it. The worst that could happen is you'll learn something new.
To add to that, once you start getting the hang of toolkit and the APIs supplied, it gets to be a lot fun and you can definitely do more with the application.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Would you recommend porting a large code base using vanilla redux to redux-toolkit? We have typed all our reducer states and actions.
I really don't think it matters what point you decide to transition from vanilla redux to redux-toolkit. Of course it's easiest to initially write all your code using the toolkit if you are planning on implementing later, just to save time and some headaches.
BUT, I also think that by writing you code in vanilla redux first, and then switching over can be very beneficial if you are newer to the react/redux realm. I've found there are ton of different ways to utilize Redux toolkit and you will come across tutorials and documentations showing it's versatility. Understanding your application, your reducers, actions, etc. will help you pick apart other code you may be learning from, so you're not just pattern following without understanding what's really going on. If you're really nervous about breaking your code, clone your repo, and try it out there first!
tldr, go for it. The worst that could happen is you'll learn something new.
To add to that, once you start getting the hang of toolkit and the APIs supplied, it gets to be a lot fun and you can definitely do more with the application.