A performant interface for rendering simple, flat lists, supporting the most handy features:
If you need section support, use <SectionList>.
Minimal Example:
This is a convenience wrapper around <VirtualizedList>,
and thus inherits the following caveats:
PureComponent which means that it will not re-render if props remain shallow-
equal. Make sure that everything your renderItem function depends on is passed as a prop that
is not === after updates, otherwise your UI may not update on changes. This includes the
data prop and parent component state.key prop on each item and uses that for the React key.
Alternatively, you can provide a custom keyExtractor prop.?ReactClass<any> #Rendered in between each item, but not at the top or bottom.
?ReactClass<any> #Rendered at the bottom of all the items.
?ReactClass<any> #Rendered at the top of all the items.
StyleObj #Optional custom style for multi-item rows generated when numColumns > 1
?Array<ItemT> #For simplicity, data is just a plain array. If you want to use something else, like an
immutable list, use the underlying VirtualizedList directly.
(data: ?Array<ItemT>, index: number) =>
{length: number, offset: number, index: number} #getItemLayout is an optional optimizations that let us skip measurement of dynamic content if
you know the height of items a priori. getItemLayout is the most efficient, and is easy to
use if you have fixed height items, for example:
Remember to include separator length (height or width) in your offset calculation if you
specify ItemSeparatorComponent.
?boolean #If true, renders items next to each other horizontally instead of stacked vertically.
(item: ItemT, index: number) => string #Used to extract a unique key for a given item at the specified index. Key is used for caching
and as the react key to track item re-ordering. The default extractor checks item.key, then
falls back to using the index, like React does.
?boolean #number #Multiple columns can only be rendered with horizontal={false}`` and will zig-zag like aflexWrap` layout. Items should all be the same height - masonry layouts are not supported.
?(info: {distanceFromEnd: number}) => void #Called once when the scroll position gets within onEndReachedThreshold of the rendered
content.
?number #?() => void #If provided, a standard RefreshControl will be added for "Pull to Refresh" functionality. Make
sure to also set the refreshing prop correctly.
?(info: {viewableItems: Array<ViewToken>, changed: Array<ViewToken>}) => void #Called when the viewability of rows changes, as defined by the
viewablePercentThreshold prop.
?boolean #Set this true while waiting for new data from a refresh.
(info: {item: ItemT, index: number}) => ?React.Element<any> #Takes an item from data and renders it into the list. Typical usage:
Provides additional metadata like index if you need it.
ViewabilityConfig #See ViewabilityHelper for flow type and further documentation.
Scrolls to the end of the content. May be janky without getItemLayout prop.
Scrolls to the item at a the specified index such that it is positioned in the viewable area
such that viewPosition 0 places it at the top, 1 at the bottom, and 0.5 centered in the
middle.
May be janky without getItemLayout prop.
Requires linear scan through data - use scrollToIndex instead if possible. May be janky
without getItemLayout prop.
Scroll to a specific content pixel offset, like a normal ScrollView.
Tells the list an interaction has occured, which should trigger viewability calculations, e.g.
if waitForInteractions is true and the user has not scrolled. This is typically called by
taps on items or by navigation actions.
You can edit the content above on GitHub and send us a pull request!
Examples # | Edit on GitHub |