v0.7.1

• style changes in Hierarchical Facets component

v0.7.0

• add Hierarchical Facets component
• fix umd-build broken for node: window is undefined

v0.6.4

• Enhanced Search UI Configuration's fieldForInstantRedirect. URL redirection to product page would be executed after user submit a keyword. This change prevents immediate redirecting when searchAsYouType is enabled.

v0.6.3

• Search field component's fieldForInstantRedirect is deprecated.
• New parameter in Search UI Configuration: fieldForInstantRedirect. This change allows using both fieldForInstantRedirect and searchResultsPageUrl at the same time.

v0.6.2

• Set "collectAnalytics=false" for all sources in autocomplete component by default. This would prevent AddSearch Analytics Dashboard to be flooded with "1 character" keyword since the original behaviour is that each search query would send a search event to AddSearch Analytics Dashboard.
• Support filtering on segmentedSearchResults component.

v0.6.1

Support for registering HandlebarJs partial.

v0.6.0

• Added support for advanced sticky facets: clicking on an item in a specific facet group will update all other facet groups except for itself.
• Added a new source in autocomplete component for custom field values.

v0.5.5

• Fixed bug in searchField setting "searchAsYouType" which prevented the autocomplete component from rendering.
• Improved Analytics for click tracking. The previous issue was that click tracking attribute "data-analytics-click" was sometimes not found in DOM tree if there were lots of nested elements.

v0.5.4

In the release v0.6.5 of the AddSearch JS-Client the filtering object URL encoding was fixed. Facet filter values were encoded by Search UI library, causing issues with double encoding. In this release Search UI library no longer URL encodes facet filter values and lets JS-Client take care of it. If you have any issues with facet filter value encoding be sure to use the version 0.6.5 of JS-Client or newer.

v0.5.3

• New setting for Search field component: fieldForInstantRedirect. If the keyword matches a custom field value in the returned search result, the user is redirected immediately to that document and the search results page is skipped.
  • For example: Your search index contains products with stock-keeping unit codes (SKU) in a custom field named "product_sku"
  • The new setting is enabled with the value fieldForInstantRedirect: "product_sku"
  • User searches with an SKU that matches to a specific product
  • The user is redirected immediately to that product page instead of search results list
• Fixed a race condition bug that caused autocomplete results being shown after search results were returned.