3 ms·
I personally don't see much value in automatic two way binding. It's a little bit of convenience that's really easy to build over React/Om if that's your cup of
by swannodette 13y ago
I personally don't see much value in automatic two way binding. It's a little bit of convenience that's really easy to build over React/Om if that's your cup of tea, http://facebook.github.io/react/docs/two-way-binding-helpers.html http://facebook.github.io/react/docs/two-way-binding-helpers.... Immutability doesn't present any challenges here.
- haberman 13y agoReactLink (which you linked to) calls setState() on the React component state when the DOM changes -- wouldn't this violate the assumptions of your shouldComponentUpdate() implementation?
- swannodette 13y agoWe don't use setState, but we have om.core/set-state! which does pretty much the same thing - an OmLink would not be very hard to do.