A performant interface for rendering basic, flat lists, supporting the most handy features:
If you need section support, use <SectionList>.
To render multiple columns, use the numColumns prop. Using this approach instead of a flexWrap layout can prevent conflicts with the item height logic.
More complex, selectable example below.
extraData={selectedId} to FlatList we make sure FlatList itself will re-render when the state changes. Without setting this prop, FlatList would not know it needs to re-render any items because it is a PureComponent and the prop comparison will not show any changes.keyExtractor tells the list to use the ids for the react keys instead of the default key property.This is a convenience wrapper around <VirtualizedList>, and thus inherits its props (as well as those of <ScrollView>) that aren't explicitly listed here, along with 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 (e.g. extraData) 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.Inherits VirtualizedList Props.
renderItemโrenderItem({
item: ItemT,
index: number,
separators: {
highlight: () => void;
unhighlight: () => void;
updateProps: (select: 'leading' | 'trailing', newProps: any) => void;
}
}): JSX.Element;
Takes an item from data and renders it into the list.
Provides additional metadata like index if you need it, as well as a more generic separators.updateProps function which let you set whatever props you want to change the rendering of either the leading separator or trailing separator in case the more common highlight and unhighlight (which set the highlighted: boolean prop) are insufficient for your use case.
item (Object): The item from data being rendered.index (number): The index corresponding to this item in the data array.separators (Object)
highlight (Function)unhighlight (Function)updateProps (Function)
select (enum('leading', 'trailing'))newProps (Object)Example usage:
<FlatList
ItemSeparatorComponent={
Platform.OS !== 'android' &&
(({highlighted}) => (
<View
style={[style.separator, highlighted && {marginLeft: 0}]}
/>
))
}
data={[{title: 'Title Text', key: 'item1'}]}
renderItem={({item, index, separators}) => (
<TouchableHighlight
key={item.key}
onPress={() => this._onPress(item)}
onShowUnderlay={separators.highlight}
onHideUnderlay={separators.unhighlight}>
<View style={{backgroundColor: 'white'}}>
<Text>{item.title}</Text>
</View>
</TouchableHighlight>
)}
/>
dataโAn array (or array-like list) of items to render. Other data types can be used by targeting VirtualizedList directly.
ItemSeparatorComponentโRendered in between each item, but not at the top or bottom. By default, highlighted and leadingItem props are provided. renderItem provides separators.highlight/unhighlight which will update the highlighted prop, but you can also add custom props with separators.updateProps. Can be a React Component (e.g. SomeComponent), or a React element (e.g. <SomeComponent />).
ListEmptyComponentโRendered when the list is empty. Can be a React Component (e.g. SomeComponent), or a React element (e.g. <SomeComponent />).
ListFooterComponentโRendered at the bottom of all the items. Can be a React Component (e.g. SomeComponent), or a React element (e.g. <SomeComponent />).
ListFooterComponentStyleโStyling for internal View for ListFooterComponent.
ListHeaderComponentโRendered at the top of all the items. Can be a React Component (e.g. SomeComponent), or a React element (e.g. <SomeComponent />).
ListHeaderComponentStyleโStyling for internal View for ListHeaderComponent.
columnWrapperStyleโOptional custom style for multi-item rows generated when numColumns > 1.
extraDataโA marker property for telling the list to re-render (since it implements PureComponent). If any of your renderItem, Header, Footer, etc. functions depend on anything outside of the data prop, stick it here and treat it immutably.
getItemLayoutโ(data, index) => {length: number, offset: number, index: number}
getItemLayout is an optional optimization that allows skipping the measurement of dynamic content if you know the size (height or width) of items ahead of time. getItemLayout is efficient if you have fixed size items, for example:
getItemLayout={(data, index) => (
{length: ITEM_HEIGHT, offset: ITEM_HEIGHT * index, index}
)}
Adding getItemLayout can be a great performance boost for lists of several hundred items. Remember to include separator length (height or width) in your offset calculation if you specify ItemSeparatorComponent.
horizontalโIf true, renders items next to each other horizontally instead of stacked vertically.
initialNumToRenderโHow many items to render in the initial batch. This should be enough to fill the screen but not much more. Note these items will never be unmounted as part of the windowed rendering in order to improve perceived performance of scroll-to-top actions.
10initialScrollIndexโInstead of starting at the top with the first item, start at initialScrollIndex. This disables the "scroll to top" optimization that keeps the first initialNumToRender items always rendered and immediately renders the items starting at this initial index. Requires getItemLayout to be implemented.
invertedโReverses the direction of scroll. Uses scale transforms of -1.
keyExtractorโ(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 item.id, and then falls back to using the index, like React does.
numColumnsโMultiple columns can only be rendered with horizontal={false} and will zig-zag like a flexWrap layout. Items should all be the same height - masonry layouts are not supported.
onRefreshโ() => void;
If provided, a standard RefreshControl will be added for "Pull to Refresh" functionality. Make sure to also set the refreshing prop correctly.
onViewableItemsChangedโCalled when the viewability of rows changes, as defined by the viewabilityConfig prop.
(callback: {changed: ViewToken[], viewableItems: ViewToken[]} => void;progressViewOffsetโSet this when offset is needed for the loading indicator to show correctly.
TyperefreshingโSet this true while waiting for new data from a refresh.
TyperemoveClippedSubviewsโUsing this property may lead to bugs (missing content) in some circumstances - use at your own risk.
When true, offscreen child views are removed from their native backing superview when offscreen. This may improve scroll performance for large lists. On Android the default value is true.
viewabilityConfigโSee ViewabilityHelper.js for flow type and further documentation.
viewabilityConfig takes a type ViewabilityConfig an object with following properties
At least one of the viewAreaCoveragePercentThreshold or itemVisiblePercentThreshold is required. This needs to be done in the constructor to avoid following error (ref):
Error: Changing viewabilityConfig on the fly is not supported
constructor (props) {
super(props)
this.viewabilityConfig = {
waitForInteraction: true,
viewAreaCoveragePercentThreshold: 95
}
}
<FlatList
viewabilityConfig={this.viewabilityConfig}
...
Minimum amount of time (in milliseconds) that an item must be physically viewable before the viewability callback will be fired. A high number means that scrolling through content without stopping will not mark the content as viewable.
Percent of viewport that must be covered for a partially occluded item to count as "viewable", 0-100. Fully visible items are always considered viewable. A value of 0 means that a single pixel in the viewport makes the item viewable, and a value of 100 means that an item must be either entirely visible or cover the entire viewport to count as viewable.
Similar to viewAreaCoveragePercentThreshold, but considers the percent of the item that is visible, rather than the fraction of the viewable area it covers.
Nothing is considered viewable until the user scrolls or recordInteraction is called after render.
viewabilityConfigCallbackPairsโList of ViewabilityConfig/onViewableItemsChanged pairs. A specific onViewableItemsChanged will be called when its corresponding ViewabilityConfig's conditions are met. See ViewabilityHelper.js for flow type and further documentation.
flashScrollIndicators()โflashScrollIndicators();
Displays the scroll indicators momentarily.
getNativeScrollRef()โgetNativeScrollRef(): React.ElementRef<typeof ScrollViewComponent>;
Provides a reference to the underlying scroll component
getScrollResponder()โgetScrollResponder(): ScrollResponderMixin;
Provides a handle to the underlying scroll responder.
getScrollableNode()โgetScrollableNode(): any;
Provides a handle to the underlying scroll node.
scrollToEnd()โscrollToEnd(params?: {animated?: boolean});
Scrolls to the end of the content. May be janky without getItemLayout prop.
Parameters:
Valid params keys are:
true.scrollToIndex()โscrollToIndex: (params: {
index: number;
animated?: boolean;
viewOffset?: number;
viewPosition?: number;
});
Scrolls to the item at 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.
Cannot scroll to locations outside the render window without specifying the getItemLayout prop.
Parameters:
Valid params keys are:
true.0 places the item specified by index at the top, 1 at the bottom, and 0.5 centered in the middle.scrollToItem()โscrollToItem(params: {
animated?: ?boolean,
item: Item,
viewPosition?: number,
});
Requires linear scan through data - use scrollToIndex instead if possible.
Cannot scroll to locations outside the render window without specifying the getItemLayout prop.
Parameters:
Valid params keys are:
true.scrollToOffset()โscrollToOffset(params: {
offset: number;
animated?: boolean;
});
Scroll to a specific content pixel offset in the list.
Parameters:
Valid params keys are:
horizontal being true, the offset is the x-value, in any other case the offset is the y-value. Required.true.