Last updated

How to change search filters in FTW

This guide describes how to change the search filters in Flex Template for Web (FTW).

The search experience can be improved by adding search filters to narrow down the results. The filters rely on listing's indexed data.

Filter types

The Flex template for web has different filter types: keyword, price, date range, select single and select multiple. Select single and select multiple filters are generic in a way that they can be used to filter search results using different kinds of data. The price and date range filters on the other hand are only used for filtering by price and date range. Keyword filter is a bit special case - there is more info about it later.

Note: price filter should be configured from src/marketplace-custom-config.js. Current maximum value for the range is set to 1000 (USD/EUR).

Filters select single and select multiple can be used with extended data. The select single one can be used to filter out search results with only one value per search parameter. The select multiple filters on the other hand can take multiple values for a single search parameter. These two filter types for extended data are implemented with two different components:

  • Select single filter: SelectSingleFilter
  • Select multiple filter: SelectMultipleFilter

Keyword filter

Keyword filter works a bit differently than other filters. It does filter search results, but it also sorts those results according to strongly listing data (title, description, and possible extended data) correlates with the search string. Currently, there is no decay function that would map keyword match correlation with distance to origin and therefore, the origin param can't be used at the same time as the keyword. You can read more about how the keyword search works from related background article.

Desktop filters

It is possible to remove location search from topbar and replace it with the keyword search or use them together (without origin param). Here's a rough guide on how to do it.

Note: search strings with only 1 or 2 letters have a longer timeout before the search query is made.

Adding a new search filter

Next we'll guide you through the steps of adding a capacity filter to the marketplace.

First step for adding a new filter is to make sure that the data being used for filtering is saved in the listing's publicData attribute. On how to achieve this, please refer to the How to extend listing data in FTW guide. Another aspect in search filters is that a search schema needs to be added to the data in order for API to index it for search. Adding search schema can be done by the Flex CLI.

Once a public data attribute is added to the listings and the data attribute is indexed, the listing searches can be filtered by that attribute by adding a query parameter that consists of a preceding "pub_" and the attribute name, so for the capacity attribute the parameter would be "pub_capacity".

Further reading on public data can be found in the How to extend listing data in FTW guide.

Note: Only top-level attributes can be indexed.

Common changes

A few common changes are required to add a select single or a select multiple filter to desktop and mobile views.

First of all, the value options for the filter need to be defined. One handy place to store these is the marketplace-custom-config.js file. The correct format is a list of objects with key and label fields:

export const capacityOptions = [
    key: 'oneToThree',
    label: '1 to 3',
    key: 'fourToSix',
    label: '4 to 6',

A few changes need to be made to the SearchPage container in order to get the filters to work.

SearchPage needs the filter options. One handy way is to add the options as a prop to the component and then set defaultProps value from config.custom (contains the marketplace-custom-config.js exports). This way tests can pass in their own values for the filter options and filter option changes won't affect tests.

SearchPageComponent.defaultProps = {
  // other default props
  capacityOptions: config.custom.capacityOptions,

SearchPageComponent.propTypes = {
  // other props
  capacityOptions: array,

Also a filter configuration needs to be added to the object returned by the filters method. The filters method combines query param name and options information of each filter so that those can be passed on to subcomponents and used for validating the filter values and rendering the filter components.

To add a filter configuration, extract the filter options from the props and set the param name as the one defined in your extended data indexing configuration:

filters() {
  const { capacityOptions } = this.props;

  return {
    capacityFilter: {
      paramName: 'pub_capacity',
      options: capacityOptions,

Final thing to do in SearchPage is to pass the filters configuration on to the components that take care of rendering the filters. This is achieved by primaryFilters and secondaryFilters props that are passed to MainPanel. The configurations are passed as an object in the same form as the configuration object in filters.

    categoryFilter: filters.categoryFilter,
    amenitiesFilter: filters.amenitiesFilter,
    capacityFilter: filters.capacityFilter,

These props are used for resolving filter states and validating the filter values. The contents are passed as props to the components that render the filters: SearchFilters, SearchFiltersPanel and SearchFiltersMobile .The difference between filters passed as primary and secondary varies in mobile and desktop views:

  • Desktop: Primary filters are shown in the top of the search view, secondary filters are rendered in a distinct panel that opens on top of search results.
  • Mobile: Both primary and secondary filters are rendered in the same modal.

Desktop filters

Desktop filters

A basic desktop filter that renders as a dropdown button on top of the search results panel is achieved using the SelectSingleFilter and SelectMultipleFilter components. To add standard desktop filters, perform the following in SearchFilters component:

  • declare a prop with the same name that you added the filter config to primaryFilters
  • resolve the filters initial value with initialValue and initialValues functions
  • render the filter by using a SelectSingleFilter or SelectMultipleFilter component inside the <div className={css.filters}> element.

Desktop filters panel

Desktop filter panel

If more filters are required than can fit into the top filter bar, the SearchFiltersPanel component can be used. It renders as a button in the top filter bar that opens a new panel that can contain a set of filters.

To use the SearchFiltersPanel, do the following:

  • declare a prop with the same name that you added the filter config to secondaryFilters
  • resolve the filters initial value with initialValue and initialValues methods
  • use the SelectSingleFilter and SelectMultipleFilter components inside the <div className={css.filtersWrapper}> element to render the filters.

Mobile filters

Mobile filters

The mobile view uses the same SelectSingleFilter and SelectMultipleFilter components as the filter panel. In this case the filter components are declared in SearchFiltersMobile. The following steps are required to add a mobile filter:

  • declare a prop with the same name that you added the filter config to primaryFilters or secondaryFilters
  • resolve the filters initial value with initialValue and initialValues methods
  • use the SelectSingleFilter and SelectMultipleFilter components inside the <div className={css.filtersWrapper}> element to render the filters.

Creating your own filter types

If you are creating new filter types note that we are using two different types of components: popup and plain. Popup components are rendered as primary dropdowns in the search view in SearchFilters. Plain components are used with SearchFiltersMobile and SearchFiltersPanel. SearchFiltersPanel opens sacondary filters in a distinct panel in order to fit additional filters to the desktop search view.

To make creating new filters easier, there are two generic components: FilterPoup and FilterPlain. These components expect that you give form fields as child component. Check SelectMultipleFilter to see how these components work.