Due to React using shallow reference equality, it's a bit too easy to cause infinite loops by putting something like a Maybe in your component state and rebuilding it in an unconditional setState inside receiveProps.
Possible fixes:
- just revert the 2.0.1 change,
findDOMNode will be slightly risky if not used within a setStateThen callback but this is a bit of an edge case anyway
- expire the slightly overloaded
receiveProps, using optional lifecycle hooks instead (bigger API change)
- something else I'm not thinking of?
Due to React using shallow reference equality, it's a bit too easy to cause infinite loops by putting something like a Maybe in your component state and rebuilding it in an unconditional
setStateinsidereceiveProps.Possible fixes:
findDOMNodewill be slightly risky if not used within asetStateThencallback but this is a bit of an edge case anywayreceiveProps, using optional lifecycle hooks instead (bigger API change)