Section List

The Section List lets you categorize its items under headers based on a given common attribute in the data objects. It works like a List.

How to use

A Section List component receives an array of data that it will loop over to create an instance of the Section List's child components for each item in the array. This can be a simple array of strings, or even an array of complex objects.

The data you pass to a Section List component's Data prop can come from a Variable if, for example, you have a fixed array of values or one populated using an API Request Action. You can also pass data to a Section List from a Fetch component on your Screen.

For each item in the array that you pass to a Section List, the List will render an instance of all child components within the Section List component. For example, if you have a Section List component that contains a single nested Text component and you pass it an array which contains 20 items, the Section List will render 20 Text components - one for each item in the array passed to the Section List.

The data for each item in the array will be available to all child components within the Section List component. The item data will be available as Section List item in any variable dropdowns for props in the component's Data tab. Any keys for the item will also be listed if you didn't skip the Test step when saving your Endpoint.

That means that our Text component above will have access to the list item's data in their variable selection dropdowns in the Data panel. So, if your array contains objects with keys such as name and description, we could pass those values to our Text component inside the Section List and each one would display their own data. Learn how to set and use the Fetch and List component in Fetching Data.

The Section Key Data prop is the most important prop as this specifies the key that is shared by all objects in the array passed to the component which is then used to render the named sections in the list.

For example, with an object like {name: "Burger", category: "Lunch"}, one could use the key category to create sections based on the value of category.

Style Properties

Style properties allow you to customize the look and feel of the component. Combinations of styles applied to components can be saved as Stylesheets to easily reuse styles throughout your app. Styles can also be set dynamically using Variables. To learn more about all the different styling properties and how they work, take a look at Intro to Styling.

Configuration Properties

PropertyDescription
Component nameThe name of the component as it appears in the Screen's component tree
InvertedIf true, reverses the direction.
Number of columnsNumber of Columns to render the items in
Refreshing colorColor of the refresh indicator
Show horizontal scroll indicatorWhen true, shows a horizontal scroll indicator. The default value is true.
Show vertical scroll indicatorWhen true, shows a vertical scroll indicator. The default value is true.
Sticky headerWhen true, header will stick to top while scrolling. On web, sticky headers only work when this component or one of its parents has a static height.
Sticky header on scrollWhen true, sticky header is hidden when scrolling down, and sticks only when scrolling up
List componentThe underlying list component to be rendered. FlatList or FlashList
HorizontalRender list horizontally
End reached thresholdHow 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.
Initial number to renderHow many items to render in the initial batch
Estimated item sizeApproximate size of the items before rendering. (Only applies when 'FlashList' is the selected list component)
Allow Touch EventsThe default behavior of the Keyboard is to dismiss when a touch component (for example, a Button) is pressed. This default behavior is set by the value Never.

Use the value Always when you want to continue to display the keyboard without dismissing the keyboard. In this scenario, to dismiss the keyboard after a touch component is pressed you will use the Dismiss Keyboard Action available on On Press trigger.

Data Properties

PropertyDescription
DataData to render in the list. Typically an array of objects
Item unique keyProvide an optional way to derive a unique key (e.g. an id or a name) for a given item in the list
Section keyKey of the data object to be used as the section

Conditional Display

You can conditionally display a component based on a given condition. Learn more about conditionally displaying components in the Conditional Display doc.

Triggers

TriggerDescription
On RefreshRuns the Actions when the element is refreshed. (i.e. pull to refresh)
On End ReachedRuns the Actions when the threshold value is reached