@elastic/search-ui-app-search-connector 0.6.0

v0.6.0

on Node.js NPM

Changes:

• Added autocomplete support to Search UI #113
  • The SearchBox component now has many additional configuration options available for using Autocomplete.
  • Autocomplete queries can now be configured much like the main search query via configuration on the SearchDriver / SearchProvider.
• SearchBox view now uses Downshift library #135
• The Result view component signature changed in order to accept primarily just a single result #82
• Query configuration options were moved out of the main configuration in SearchDriver / SearchProvider and are now nested under a searchQuery field. Described in Autocomplete Spec: #113, commit 902b431
• searchQuery configuration allows adding static request state configuration to search queries, like filters, etc., which are always applied to queries regardless of the current application state. Describe in Autocomplete spec: #113, commit: 121616c
• Fixed a number of issues that were occurring when using custom views: #160
• Added a debug option to SearchDriver #169
• Fixed unmount / history issues when using client side routing: #174 #177 #178

Breaking Changes:

• The SearchBox.js component in react-search-ui-views - This component now uses the Downshift (https://github.com/downshift-js/downshift) library in order to support autocomplete. Since the markup has changed, it is possible that styles that target specific html structures or classes may no longer be valid.
• onChange prop in the SearchBox.js component in react-search-ui-views is a function that now accepts a string value, it no longer accepts a browser event.
• The signature for renderResults in the Result.js component has changed. Instead of receiving the props url, title, and fields, it simply receives a result prop.
• Likewise, the Result.js component in react-search-ui-views component has changed, it now accepts a single result prop, and not url, title, and fields.
• Query configuration should no longer be passed directly to a SearchDriver or SearchProvider, they should be nested under a property called "searchQuery". This affects the following properties:
  • facets
  • disjunctiveFacets
  • disjunctiveFacetsAnalyticsTags
  • conditionalFacets
  • search_fields
  • result_fields