Logan Daniels c46ca60e3f Make FlatList's renderItem return React.Node ...

Summary:
Flow typing can be annoying because the `renderItem` prop for FlatList always has to specifically be of type `React.Element`.

Since really we just want to return something renderable, it should be fine to type this as `React.Node` instead.

I'm not sure if this is valid, but it seems like since we just need to implant the `key` property, we should be able to accomplish this with a `React.Fragment` wrapper instead of needing to call `cloneElement`. Looking for feedback on if this is a sensible fix.

Changelog:
[General][Changed] Updated FlatList's renderItem Flow type from React.Element<any> to React.Node

Reviewed By: sahrens

Differential Revision: D14814805

fbshipit-source-id: ce6793dea5a92619babe048dcfddee0e4519979c

2019-04-08 12:55:09 -07:00

..

__flowtests__

Update copyright headers to yearless format

2018-09-11 15:33:07 -07:00

__tests__

Remove wrapper around ListEmptyComponent (#24339)

2019-04-08 12:49:55 -07:00

FillRateHelper.js

Deploy 0.94 to xplat

2019-03-06 14:57:30 -08:00

FlatList.js

Make FlatList's renderItem return React.Node

2019-04-08 12:55:09 -07:00

SectionList.js

@allow-large-files [flow] update to v0.83

2018-10-13 01:32:48 -07:00

ViewabilityHelper.js

Fixes 'Invalid render range' crash (#22847)

2019-01-21 01:58:54 -08:00

VirtualizedList.js

Remove wrapper around ListEmptyComponent (#24339)

2019-04-08 12:49:55 -07:00

VirtualizedSectionList.js

- VirtualizedSectionList/SectionList: replace enableVirtualization prop annotation by correct underlying disableVirtualisation of VirtualizedList (#24312)

2019-04-04 14:32:39 -07:00

VirtualizeUtils.js

Use invariant instead of fbjs/lib/invariant

2018-12-03 00:07:02 -08:00