SingleList

SingleList creates a single selection based list UI component that is connected to a database field.

Example uses:

• select a category item from a list of categories in an e-commerce website.
• select a cuisine item from a list of cuisine items in a food delivery app.

Usage

Basic Usage

<template>
	<single-list componentId="CitySensor" dataField="group.group_city.raw" title="Cities" />
</template>

Usage With All Props

<template>
    <single-list
        componentId="CitySensor"
        compoundClause="filter"
        dataField="group.group_city.raw"
        title="Cities"
        sortBy="count"
        defaultValue="London"
        selectAllLabel="All Cities"
        placeholder="Search City"
        filterLabel="City"
        :size="100"
        :showRadio="true"
        :showCount="true"
        :showSearch="true"
        :showFilter="true"
        :URLParams="false"
        :react="{ and: ['CategoryFilter', 'SearchFilter'] }"
        :endpoint="{
            url:'https://appbase-demo-ansible-abxiydt-arc.searchbase.io/recipes-demo/_reactivesearch.v3',
            headers: {
                // put relevant headers
            },
            method: 'POST'
        }"        
    />
</template>

Props

componentId

unique identifier of the component, can be referenced in other components' react prop.

compoundClause

Configure whether the DSL query is generated with the compound clause of must or filter. If nothing is passed the default is to use must. Setting the compound clause to filter allows search engine to cache and allows for higher throughput in cases where scoring isn’t relevant (e.g. term, geo or range type of queries that act as filters on the data)

This property only has an effect when the search engine is either elasticsearch or opensearch.

Note: compoundClause is supported with v8.16.0 (server) as well as with serverless search.

endpoint

endpoint prop provides the ability to query a user-defined backend service for this component, overriding the data endpoint configured in the ReactiveBase component. Accepts the following properties:

• url String [Required] URL where the data cluster is hosted.
• headers Object [optional]
  set custom headers to be sent with each server request as key/value pairs.
• method String [optional]
  set method of the API request.
• body Object [optional]
  request body of the API request. When body isn't set and method is POST, the request body is set based on the component's configured props.

• Overrides the endpoint property defined in ReactiveBase.
• If required, use transformResponse prop to transform response in component-consumable format.

dataField

data field to be connected to the component's UI view. The list items are filtered by a database query on this field. This field is used for doing an aggregation and returns the result. We're using a .raw multifield here. You can use a field of type keyword or not_analyzed depending on your Elasticsearch cluster.

nestedField

use to set the nested mapping field that allows arrays of objects to be indexed in a way that they can be queried independently of each other. Applicable only when dataField is a part of nested type.

title

title of the component to be shown in the UI.

size

number of list items to be displayed.

Note:

1. Appbase users should use the aggregationSize prop instead. The size prop would only set the size for hits not the aggregations.
2. We recommend Appbase users to not use the size prop unless they are using hits because it can impact the query performance.

aggregationSize

To set the number of buckets to be returned by aggregations.

sortBy

sort the list items by one of count, asc, desc. Defaults to count, which sorts the list by the frequency of count value, most first.

defaultValue

pre-select an item from the list.

value

sets the current value of the component. It sets the value (on mount and on update). Use this prop in conjunction with the change event.

selectAllLabel

add an extra Select all item to the list with the provided label string.

showRadio

show radio button icon for each list item. Defaults to true.

showCount

show count value of the number of occurences besides a list item. Defaults to true.

showFilter

show as filter when a value is selected in a global selected filters view. Defaults to true.

filterLabel

An optional label to display for the component in the global selected filters view. This is only applicable if showFilter is enabled. Default value used here is componentId.

showMissing

defaults to false. When set to true it also retrives the aggregations for missing fields under the label specified by missingLabel.

missingLabel

defaults to N/A. Specify a custom label to show when showMissing is set to true.

showSearch

whether to show a searchbox to filter the list items locally. Defaults to true.

placeholder

placeholder to be displayed in the searchbox, only applicable when the showSearch prop is set to true. When applicable, the default placeholder value is set to "Search".

URLParams

enable creating a URL query string parameter based on the selected value of the list. This is useful for sharing URLs with the component state. Defaults to false.

renderItem

customize the rendered list via a function or slot-scope which receives the item label, count and isChecked & expects a JSX or String back. For example:

<single-list>
    <template #renderItem="{ label, count }">
        <div>
            {{label}}
            <span :style="{ marginLeft: 5, color: 'dodgerblue' }">
                {{count}}
            </span>
        </div>
    </template>
</single-list>

render

an alternative callback function to renderItem, where user can define how to render the view based on all the data changes.
It accepts an object with these properties:

• loading: boolean indicates that the query is still in progress
• error: object An object containing the error info
• data: array An array of results obtained from the applied query.
• rawData object An object of raw response as-is from elasticsearch query.
• value: array current selected values.
• handleChange: function A callback function can be used to mark the list value as selected.

You can use render as a slot as shown below:

<single-list
    :showSearch="false"
    componentId="BookSensor"
    data-field="original_series.raw"
>
    <template #render="{ data, handleChange }">
        <div class="suggestions">
            <ul>
                <li
                    style="{ background-color: highlightedIndex ? 'grey' : 'transparent' }"
                    v-for="suggestion in (data || [])"
                    :key="suggestion._id"
                    v-on:click="handleChange(suggestion.key)"
                >
                    {{ suggestion.key }}
                </li>
            </ul>
        </div>
    </template>
</single-list>

renderError

can be used to render an error message in case of any error.

    <template #renderError="error">
        <div>Something went wrong!<br />Error details<br />{{ error }}</div>
    </template>

renderNoResults

show custom message or component when no results found.

<template #renderNoResults>
	<h4>No Results Found!</h4>
</template>

<!-- or -->

<single-list
	...
	:renderNoResults="renderNoResults"
/>

export default {
	...,
	method: {
		renderNoResults() {
			return 'Try Again';
		}
	},
}

transformData

allows transforming the data to render inside the list. You can change the order, remove, or add items, transform their values with this method. It provides the data as param which is an array of objects of shape { key: , doc_count: } and expects you to return the array of objects of same shape.

enableStrictSelection

When set to true, a selected option can't be unselected. Although, it is possible to change the selected option. Defaults to false.

Demo

Styles

SingleList component supports innerClass prop with the following keys:

• title
• input
• list
• radio
• label
• count

Read more about it here.

Extending

SingleList component can be extended to

1. customize the look and feel with className,
2. update the underlying DB query with customQuery,
3. connect with external interfaces using beforeValueChange, value-change and query-change,
4. specify how options should be filtered or updated using react prop.

<template>
	<single-list
		className="custom-class"
		:customQuery="getCustomQuery"
		:beforeValueChange="handleBeforeValueChange"
		:react="react"
		@value-change="handleValueChange"
		@query-change="handleQueryChange"
	/>
</template>
<script>
	export default {
		name: 'app',
		methods: {
			getCustomQuery: (value, props) => {
				return {
					query: {
						match: {
							data_field: 'this is a test',
						},
					},
				};
			},
			handleBeforeValueChange: value => {
				// called before the value is set
				// returns a promise
				return new Promise((resolve, reject) => {
					// update state or component props
					resolve();
					// or reject()
				});
			},
			handleValueChange: value => {
				console.log('current value: ', value);
				// set the state
				// use the value with other js code
			},
			handleQueryChange: (prevQuery, nextQuery) => {
				// use the query with other js code
				console.log('prevQuery', prevQuery);
				console.log('nextQuery', nextQuery);
			},
		},
		computed: {
			react() {
				return {
					and: ['pricingFilter', 'dateFilter'],
					or: ['searchFilter'],
				};
			},
		},
	};
</script>

className

CSS class to be injected on the component container.

customQuery

is a callback function which accepts component's current value as a parameter and returns the data query to be applied to the component, as defined in Elasticsearch Query DSL. Note: customQuery is called on value changes in the SingleList component as long as the component is a part of react dependency of at least one other component.

defaultQuery

takes value and props as parameters and returns the data query to be applied to the source component, as defined in Elasticsearch Query DSL. Note: defaultQuery doesn't get leaked to other components.

beforeValueChange

is a callback function which accepts component's future value as a parameter and returns a promise. It is called everytime before a component's value changes. The promise, if and when resolved, triggers the execution of the component's query and if rejected, kills the query execution. This method can act as a gatekeeper for query execution, since it only executes the query after the provided promise has been resolved.

Note:

If you're using Reactivesearch version >= 1.1.0, beforeValueChange can also be defined as a synchronous function. value is updated by default, unless you throw an Error to reject the update. For example:

beforeValueChange = value => {
    // The update is accepted by default
    if (value === 'In Death') {
        // To reject the update, throw an error
        throw Error('Selected value should not be equal to In Death.');
    }
};

react

specify dependent components to reactively update SingleList's options.

• key String one of and, or, not defines the combining clause.
  • and clause implies that the results will be filtered by matches from all of the associated component states.
  • or clause implies that the results will be filtered by matches from at least one of the associated component states.
  • not clause implies that the results will be filtered by an inverse match of the associated component states.
• value String or Array or Object
  • String is used for specifying a single component by its componentId.
  • Array is used for specifying multiple components by their componentId.
  • Object is used for nesting other key clauses.

index

The index prop can be used to explicitly specify an index to query against for this component. It is suitable for use-cases where you want to fetch results from more than one index in a single ReactiveSearch API request. The default value for the index is set to the app prop defined in the ReactiveBase component.

Events

change

is an event that accepts component's current value as a parameter. It is called when you are using the value prop and the component's value changes. This event is useful to control the value updates of search input.

<template>
    <single-list
        // ...other props
        value="value"
        @change="handleChange"
    />
</template>

<script>
export default {
name: 'app',
    data() {
        return {
            value: ""
        }
    },
    methods: {
        handleChange(value) {
            this.value = value;
        }
    }
};
</script>

query-change

is an event which accepts component's prevQuery and nextQuery as parameters. It is called everytime the component's query changes. This event is handy in cases where you want to generate a side-effect whenever the component's query would change.

value-change

is an event which accepts component's current value as a parameter. It is called everytime the component's value changes. This event is handy in cases where you want to generate a side-effect on value selection. For example: You want to show a pop-up modal with the valid discount coupon code when a list item is selected in a "Discounted Price" SingleList.

error

gets triggered in case of an error and provides the error object, which can be used for debugging or giving feedback to the user if needed.

Examples

SingleList with default props