Things I wish I knew about state management when I started writing React apps
1–10 of 335 posts
Re: Things I wish I knew about state management when I started writing React apps
#2OP comment on Reddit:
>https://old.reddit.com/r/javascript/comments/f1jop9/6_things...
Re: Things I wish I knew about state management when I started writing React apps
#3I’ve been learning React and have been avoiding Redux out of fear of complexity. However, as my app grows more complex, the need for a global state manager becomes more apparent. Time to start learning Redux today :)
Re: Things I wish I knew about state management when I started writing React apps
#4I’ve been learning React and have been avoiding Redux out of fear of complexity. However, as my app grows more complex, the need for a global state manager becomes more apparent. Time to start learning Redux today :)
Or mobx :)
Re: Things I wish I knew about state management when I started writing React apps
#5Bounced around 2 projects in the last 12 months, one Angular and one React, that are using the Flux pattern. It is a real bitch to unit test anything but the individual pieces, which ends up being kind of meaningless.
Re: Things I wish I knew about state management when I started writing React apps
#6I’ve been learning React and have been avoiding Redux out of fear of complexity. However, as my app grows more complex, the need for a global state manager becomes more apparent. Time to start learning Redux today :)
Try zustand!
Re: Things I wish I knew about state management when I started writing React apps
#7I’ve been learning React and have been avoiding Redux out of fear of complexity. However, as my app grows more complex, the need for a global state manager becomes more apparent. Time to start learning Redux today :)
It's not the amount of complexity that leads to needing Redux, it's the type of complexity. You can go a long way on keeping state in the nearest common ancestor of the components that need to share it.
Re: Things I wish I knew about state management when I started writing React apps
#8What's the deal with the recommendation to use some library for managing forms? I've been working with React almost since its initial release and I've built some pretty complex forms... yet form libraries remain the one thing I've never really seen a need for.
At the very least, using something like formik shouldn't be a necessity. There should be some qualifier that it's only really needed for very complex forms. Or am I missing something?
Re: Things I wish I knew about state management when I started writing React apps
#9This is one area I have to give a huge tip of the hat to Flutter and Provider, BLoC pattern using streams (and transform streams!) and RX generally.
It's been a lot easier to comprehend coming from C than the React options.
Re: Things I wish I knew about state management when I started writing React apps
#10I’ve been learning React and have been avoiding Redux out of fear of complexity. However, as my app grows more complex, the need for a global state manager becomes more apparent. Time to start learning Redux today :)
I never understood why redux was considered "hard" - it basically keeps track of a plain javascript object that you can read/write across a react app