3 ms·
> I question whether people use it in large scale production. We tried to, and removed it within 4 weeks of development with it, for all of the reasons you men
by girvo 10y ago
> I question whether people use it in large scale production.
We tried to, and removed it within 4 weeks of development with it, for all of the reasons you mentioned. It conceptually doesn't map to our Redux model, and new developers struggled with it because of that. I ended up writing my own "wrapper" to do something similar, but to be honest for most of our form state it is handled within the components themselves (via this.state and friends) and only sent to Redux once validated. React's built-in state handling is still useful, specifically for these sorts of things.
- acemarke 10y agoI'd be interested in seeing what you put together. Is that available somewhere?
- davidjnelson 10y agoWhat are the pros/cons of setstate vs a batched state subtree for each component and an aggregate state subtree for each component that matched each form parent, specified by a string to a higher order component for the parent form and a string for each component used to model html5 form inputs?
- acemarke 10y agoAh... you lost me on that statement. Can you give me an example of what you're picturing?