Spencer Ahrens 5c856150ff Kill shouldItemUpdate ...

Summary:
It was just adding unnecessary complexity. Users should just use standard React perf best practices, like `PureComponent` and `shouldComponentUpdate`.

This should be backwards compatible - existing `shouldItemUpdate` usage will just be ignored and should consider migrating to this pattern:

```
class MyItem extends React.PureComponent {
  _onPress = () => {
  	this.props.onPressItem(this.props.id);
  };
  render() {
    return (
      <SomeOtherWidget title={this.props.title} onPress={this._onPress} />
    )
  }
}
...
_renderItem = ({item}) => (
  <MyItem onPressItem={this._onPressItem} title={item.title} id={item.id} />
);
```

Which will automatically prevent re-renders unless the relavent data changes.

Reviewed By: yungsters

Differential Revision: D4730599

fbshipit-source-id: 0f61efe96eb4d95bb3b7c4ec889e3e0e34436e56

2017-03-21 22:30:30 -07:00

..

2048

Update React Native minimum OS version to iOS8

2016-09-01 19:43:47 -07:00

Movies

Fix Issue with network errors

2017-03-05 19:02:54 -08:00

TicTacToe

Apply auto-formatter for BUCK files in fbandroid.

2017-02-27 14:04:56 -08:00

UIExplorer

Kill shouldItemUpdate

2017-03-21 22:30:30 -07:00

.eslintrc

…