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 ScrollView Props, unless it is nested in another FlatList of same orientation.
renderItem
renderItem({ item, index, separators });
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.
| Type |
|---|
| function |
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
For simplicity, data is a plain array. If you want to use something else, like an immutable list, use the underlying VirtualizedList directly.
| Type |
|---|
| array |
ItemSeparatorComponentRendered 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.
| Type |
|---|
| component |
ListEmptyComponentRendered when the list is empty. Can be a React Component (e.g. SomeComponent), or a React element (e.g. <SomeComponent />).
| Type |
|---|
| component, element |
ListFooterComponentRendered at the bottom of all the items. Can be a React Component (e.g. SomeComponent), or a React element (e.g. <SomeComponent />).
| Type |
|---|
| component, element |
ListFooterComponentStyleStyling for internal View for ListFooterComponent.
| Type |
|---|
| View Style |
ListHeaderComponentRendered at the top of all the items. Can be a React Component (e.g. SomeComponent), or a React element (e.g. <SomeComponent />).
| Type |
|---|
| component, element |
ListHeaderComponentStyleStyling for internal View for ListHeaderComponent.
| Type |
|---|
| View Style |
columnWrapperStyleOptional custom style for multi-item rows generated when numColumns > 1.
| Type |
|---|
| View Style |
extraDataA 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.
| Type |
|---|
| any |
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.
| Type |
|---|
| function |
horizontalIf true, renders items next to each other horizontally instead of stacked vertically.
| Type |
|---|
| boolean |
initialNumToRenderHow 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.
| Type | Default |
|---|---|
| number | 10 |
initialScrollIndexInstead 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.
| Type |
|---|
| number |
invertedReverses the direction of scroll. Uses scale transforms of -1.
| Type |
|---|
| boolean |
keyExtractor(item: object, 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.
| Type |
|---|
| function |
numColumnsMultiple 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.
| Type |
|---|
| number |
onEndReached(info: {distanceFromEnd: number}) => void
Called once when the scroll position gets within onEndReachedThreshold of the rendered content.
| Type |
|---|
| function |
onEndReachedThresholdHow far from the end (in units of visible length of the list) the bottom edge of the list must be from the end of the content to trigger the onEndReached callback. Thus a value of 0.5 will trigger onEndReached when the end of the content is within half the visible length of the list.
| Type |
|---|
| number |
onRefresh() => void
If provided, a standard RefreshControl will be added for "Pull to Refresh" functionality. Make sure to also set the refreshing prop correctly.
| Type |
|---|
| function |
onViewableItemsChangedCalled when the viewability of rows changes, as defined by the viewabilityConfig prop.
| Type |
|---|
| (callback: { changed: array of ViewTokens, viewableItems: array of ViewTokens }) => void |
progressViewOffsetSet this when offset is needed for the loading indicator to show correctly.
| Type |
|---|
| number |
refreshingSet this true while waiting for new data from a refresh.
| Type |
|---|
| boolean |
removeClippedSubviewsThis may improve scroll performance for large lists. On Android the default value is true.
Note: May have bugs (missing content) in some circumstances - use at your own risk.
| Type |
|---|
| boolean |
viewabilityConfigSee ViewabilityHelper.js for flow type and further documentation.
| Type |
|---|
| ViewabilityConfig |
viewabilityConfig takes a type ViewabilityConfig an object with following properties
| Property | Type |
|---|---|
| minimumViewTime | number |
| viewAreaCoveragePercentThreshold | number |
| itemVisiblePercentThreshold | number |
| waitForInteraction | boolean |
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.
viewabilityConfigCallbackPairsList 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.
| Type |
|---|
| array of ViewabilityConfigCallbackPair |
flashScrollIndicators()flashScrollIndicators();
Displays the scroll indicators momentarily.
getNativeScrollRef()getNativeScrollRef();
Provides a reference to the underlying scroll component
getScrollResponder()getScrollResponder();
Provides a handle to the underlying scroll responder.
getScrollableNode()getScrollableNode();
Provides a handle to the underlying scroll node.
recordInteraction()recordInteraction();
Tells the list an interaction has occurred, 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.
scrollToEnd()scrollToEnd(([options]: { animated: boolean }));
Scrolls to the end of the content. May be janky without getItemLayout prop.
Parameters:
| Name | Type |
|---|---|
| params | object |
Valid params keys are:
true.scrollToIndex()scrollToIndex(params);
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.
Note: Cannot scroll to locations outside the render window without specifying the
getItemLayoutprop.
Parameters:
| Name | Type |
|---|---|
| params Required
|
object |
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);
Requires linear scan through data - use scrollToIndex instead if possible.
Note: Cannot scroll to locations outside the render window without specifying the
getItemLayoutprop.
Parameters:
| Name | Type |
|---|---|
| params Required
|
object |
Valid params keys are:
true.scrollToOffset()scrollToOffset(params);
Scroll to a specific content pixel offset in the list.
Parameters:
| Name | Type |
|---|---|
| params Required
|
object |
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.
© 2022 Facebook Inc.
Licensed under the Creative Commons Attribution 4.0 International Public License.
https://reactnative.dev/docs/flatlist