From 71444ff133a77bbec9a52eba6f6a1c35edcb8557 Mon Sep 17 00:00:00 2001
From: Travis CI
() => renderable
The header and footer are always rendered (if these props are provided) on every render pass. If they are expensive to re-render, wrap them in StaticContainer or other mechanism as appropriate. Footer is always -at the bottom of the list, and header at the top, on every render pass.
(rowData, sectionID, rowID, highlightRow) => renderable -Takes a data entry from the data source and its ids and should return +at the bottom of the list, and header at the top, on every render pass.
(rowData, sectionID, rowID, highlightRow) => renderable
Takes a data entry from the data source and its ids and should return a renderable component to be rendered as the row. By default the data is exactly what was put into the data source, but it's also possible to provide custom extractors. ListView can be notified when a row is @@ -53,8 +52,7 @@ are rendered. Defaults to returning a ScrollView with the given props.
(sectionID, rowID, adjacentRowHighlighted) => renderable -If provided, a renderable component to be rendered as the separator +header.
(sectionID, rowID, adjacentRowHighlighted) => renderable
If provided, a renderable component to be rendered as the separator below each row but not the last row if there is a section header below. Take a sectionID and rowID of the row above and whether its adjacent row is highlighted.
How early to start rendering rows before they come on screen, in