Releases: AddSearch/search-ui
Releases · AddSearch/search-ui
v0.5.2
v0.5.1
- Store the sort parameter in URL for proper behavior when the page is, for example, reloaded
- Added possibility to collect search analytics in the autocomplete component for sources with the type AddSearchUI.AUTOCOMPLETE_TYPE.SEARCH. Analytics collection can be enabled with the new setting collectSearchAnalytics
v0.5.0
- Changed behavior: The matchAllQuery setting won't make search queries for the autocomplete box anymore. Only for the main search.
- New setting for the Search field component: onfocusAutocompleteMatchAllQuery. With this setting, focusing an empty search field fires a match all query for the autocomplete box. Intended use is to show recommended search results to the user, before she has typed anything
- Optimized rendering: Components won't be re-rendered if the output HTML wouldn't change
- API call optimization
v0.4.21
- Added the number of search result pages returned (totalPages) to the data object accessible by the pagination component
- Clarified searchResults component's documentation on how clicks are collected for analytics
v0.4.20
- Added a setting to disable browser history: updateBrowserHistory. This comes in handy if you have secondary (or tertiary..) Search UI instances on a single page
- Modified search results template to show the page URL if there is no title
v0.4.19
Fixed a bug in infinite scroll that could cause browser window scrolling to top unintentionally.
v0.4.18
v0.4.17
Two bug fixes in the autocomplete component:
- Pagination was not reset when the keyword changed
- Autocomplete box with infinite scroll was not hidden properly on blur event
v0.4.16
- Added a new configuration option
baseFilters
to define filters that are applied in every search query. Users can't see or disable baseFilters - Added support for URLs with query parameters to the
searchResultsPageUrl
setting
v0.4.14
Added a new configuration option to define the query parameter name for keyword (default: ?search=keyword).