v0.4.13

• Clear segmented search when the keyword is erased
• Fix race condition bug with search-as-you-type implementations when the keyword is erased while search request is pending

v0.4.12

New setting for the pagination component to control scroll behavior after the page is changed: onResultsScrollTo

v0.4.11

New setting for filters component to set the order of results when the filter value changes: setSorting. For example, different tabs could have different sort orders.

  setSorting: {
    field: 'date',
    order: 'desc'
  }

v0.4.10

Added a setting to disable automatic analytics collection: collectAnalytics

v0.4.9

Fixed an issue with sticky facets where the setting wasn't applied in some scenarios.

v0.4.8

• Range filters: Filter by numeric or date custom fields. For example, let users search for products with price between $100 and $200. See example.
• Sticky facets: Possibility to select multiple facets from a single facet group with the new sticky setting. See example.
• Improved browser history. Null query parameters won't be rewritten with an empty value anymore (i.e. ?foo won't be changed to ?foo=

v0.4.7

Support x-www-form-urlencoded keywords in URL. I.e. spaces can be escaped with a plus sign or with %20

v0.4.6

• Fixed infinite scroll in autocomplete component that broke down in v0.4.5
• Refactored state management: Now it's possible to have multiple self-contained AddSearchUI instances on a single web page

v0.4.5

• Improved autocomplete component's visibility logic. Now the component is re-shown if the component has content and the search field is focused
• New autocomplete example with combination of search suggestions and instant search results
• Fixed an issue with browser history where the hash part was removed from the URL unintentionally

v0.4.2

New component: segmentedSearchResults. This component can be used to show several search results lists having different filters and/or results from different indices. See example.