Most UI components are state-less and should render the same markup given the same props. By helping react with via shouldComponentUpdate can give rather large performance boost in complex applications.
Sure. The library was built before the introduction of PureComponent and it hasn't been updated to this new "component". But a PR to add it would be a great idea.
Why have you not utilized shouldComponentUpdate and/or React's
PureComponent
?Most UI components are state-less and should render the same markup given the same props. By helping react with via
shouldComponentUpdate
can give rather large performance boost in complex applications.Would a contribution to fix this be accepted?