redux-form

See this article: https://medium.com/@codesponsor/fighting-for-open-source-sus... Here's an example of what it looks like: https://github.com/erikras/redux-form

Going through this now. It's worth highlighting that Flux is just one pattern for centralized state management in React. I see a lot of new projects being built on Redux, and Redux is (technically) not Flux: http://redux.js.org/docs/introduction/PriorArt.html If you do decide to go the Redux route, I recommend taking a look at redux-form: https://github.com/erikras/redux-form, as complicated form logic is one of the biggest reasons for us to work on a centralized state store.

FWIW redux-form v6 changes this: https://github.com/erikras/redux-form/releases I've been using redux-form in large production app, btw, and have mostly found it nice, but am looking forward to migrating to the new version.

I've used it in a couple of form-heavy production projects and found it to be good, I find the API pretty easy to work with and it handles things like async validation pretty nicely (I use it in combination with yup for validating the form object: https://github.com/jquense/yup). I can honestly say it has almost made working with forms enjoyable ;) A definite high point of my time with it was when a requirement came along to allow users to resume signup - because all the form state was in the Redux store already, it was simply a case of serializing that and putting it in localStorage (or wherever), then reloading it as the initialState. There are performance issues to be aware of if your form gets too large, caused by the "top down re-render" effect of having the top level ReduxForm HOC connected to the form state and therefore re-renderi

First: Redux is _not_ dogmatic about putting every last bit of your state into Redux. It is entirely up to you how much or how little goes into Redux. (This question comes up all the time, which is why I added it the the Redux FAQ [0] ). So yes, there are absolutely times when it makes sense to keep data, such as frequent user input updates, in local component state, and only dispatch an action later. In fact, a while back I put together a wrapper component that does exactly that [1]. Made a few tweaks since then that I haven't added to the proof-of-concept in the gist, but the basic idea is there. I do have a number of articles on React and forms in my React/Redux links list [2], but at the moment I don't think any of them specifically deal with Redux usage. Might be interesting to look through some of the apps listed in my real-wor

I'd suggest looking at https://github.com/erikras/redux-form

The official Redux answer way is to use app state for everything. See libraries like https://github.com/erikras/redux-form which move all the field state into your app state. Personally I break that rule when I know I can. The only other state I can think of is animation state - but using css transition animations has just worked out for me so far.

Thanks for the valuable tips! Currently, my biggest 'bottleneck' when developing React applications is managing complex forms. Right now I'm using redux-form [0] which is a great tool, but not very performant on dynamic deep/complex forms (more info and partial hacks here: [1]). Other than that, I don't have performance problems, but I'm curious when will I hit Redux limitations (single store sounds great from the conceptual point of view, but I'm not sure about the performance one). Also, can second ImmutableJS recommendation, after a while of using it's completely natural to use. [0] https://github.com/erikras/redux-form/ [1] https://github.com/erikras/redux-form/issues/529