v0.6.5

The contents of the filtering object were not properly URL encoded causing filter criteria with some special characters such as ampersand to not work properly. Fixed.

v0.6.4

Enhanced internal API fetch function to support upcoming faceting improvements in the Search UI library.

v0.6.3

Added a function to control the default logical operator in search (and/or): setSearchOperator

v0.6.2

Added a function to control search result cache TTL for server side caching: setCacheResponseTime.

v0.6.1

Fixed a bug with retry type fuzzy matching causing the second API fetch not firing.

v0.6.0

New setting enableLogicalOperators to control if user specified logical operators (and/or/not) should be processed in the search queries like "cat and dog". The default value is false, so logical operators are not processed and the words are treated as literal strings.

Before the release v0.6.0 there hasn't been a setting to control the processing of logical operators. The default behaviour was to process them, so to keep your existing app's behaviour intact, enable the new setting:

client.enableLogicalOperators(true);

v0.5.2

Added a function to set the hostname for API calls. This can be used, for example, with dedicated environments with customer-specific API host.

v0.5.1

Updated dependencies.

v0.5.0

Added functions to use Indexing API to create, update, fetch, and delete single documents or batches of documents. The full indexing API documentation can be found at addsearch.com

Example of indexing a document:

// Define a document (schemaless)
const doc = {
  custom_fields: {
    'name': 'Example product',
    'description': 'Description for the example product',
    'price_cents': 599,
    'average_customer_rating': 4.5
  }
};

// Save the document
client.saveDocument(doc)
  .then(response => {
    console.log(response);
  })
  .catch(error => {
    console.log(error);
  });

v0.4.3

Added support for field statistics. With this feature, you can add minimum, maximum, and average values of numerical or date-based custom fields to the search response. See documentation