We use props to access and transfer the data between components , There could be a situation where we have more complicated nested components and that is the time you don’t want to use props because…

TowardsDev's platform is a resource for developers, offering insights into software development, coding tutorials, and technology news. Through articles, tutorials, and coding challenges, TowardsDev offers insights into programming languages, development frameworks, and best practices in software engineering. Readers can learn about algorithms, data structures, and problem-solving techniques to enhance their coding skills and prepare for technical interviews.

Towards Dev

In this article i will get you through redux concepts and how it works and how we can really use it. Redux is a libra r y to manage global state ,we use redux in libraries and freamworks like react , angular ,… and we use reduX-thunk for our actions.

Redux is easier than you think!

1.install packages and libraries that you need

3.creating store and provider in root file(src/index.js)

It seems redux persist is better wrapped around individual reducers than the root. Sure you get a bit of duplication for every reducer you want to persist this way but you don’t end up with a bunch of black listed state reducers in the config. I’d be selective with persisted storage because it’s a pain to manage stale data structures, unexpected browser cleanups due to low storage or implementation bugs (looking at you safari).
Applying too much DRY can harm you in the long run if you’re not careful so don’t don’t repeat yourself all the time ;) think before you do that.

The article is a great guide to understand redux and the old ways of working with redux. Nowadays, though, redux-toolkit is the official and recommended way to use it with react. <a href="https://redux-toolkit.js.org/" target="_blank" rel="noopener nofollow">https://redux-toolkit.js.org/</a> Also, the docs are great.