News for hackers. Stuff that matters.
Re:Why is setState asynchronous? by sarreph on Thursday January 25, 2018 @03:48PM (#16234516)
I agree with your 'stateless' approach for many use cases that are otherwise 'muddied' by unnecessary component state.

However, instead of calling forceUpdate(), I was under the impression that componentWillReceiveProps(props) was more efficient?

Perhaps I'm wrong on that one, though... Just that forceUpdate() is an approach that is officially encouraged against.[0]

[0] - https://reactjs.org/docs/react-component.html#forceupdate

There are no comments on this comment yet.