[go: nahoru, domu]

Skip to content

Tags: 130903/algoliasearch-client-javascript

Tags

3.27.1

Toggle 3.27.1's commit message
3.27.1

* FIX: `client.searchForFacetValues` in older browsers
  * we use the polyfill implementation of Promise.all now instead of the native in 3.27.0
* FIX: `index.saveRule` throw when no objectID is given
* FEAT: deprecate index API key methods in favor of client ones
  * these methods will be removed, since you can add index restrictions to client API keys

3.27.0

Toggle 3.27.0's commit message
3.27.0

* FEAT: add client.searchForFacetValues
  * this allows to request multiple search for facet values in a single call
  * note that this will do multiple requests (one per query)

3.26.0

Toggle 3.26.0's commit message
3.26.0

FEAT: allow disabling of dsn

in some cases (backend search while you do have global DSN), you want to disable DSN to avoid a round-robin around the whole world if DNS can't be resolved as expected, for example on GCP. (algolia#675)

3.25.1

Toggle 3.25.1's commit message
3.25.1

2018-03-08 3.25.1
  * FIX: fix protocol detection introduced in 3.25.1

3.25.0

Toggle 3.25.0's commit message
3.25.0

FEAT: use https by default (algolia#670)

For very old devices https can be slow
we defaulted to sending API requests over http on http sites. This is now not really a performance bottleneck anymore, so https is now default, unless specified differently when initializing.

3.24.12

Toggle 3.24.12's commit message
3.24.12

2018-02-28 3.24.12
  * FIX: Handle Node.js network errors more precisely (algolia#669)

3.24.11

Toggle 3.24.11's commit message
3.24.11

* FIX: allow `index.getSettings` without any arguments
    * this was a regression in 3.24.10
    * added tests

3.24.10

Toggle 3.24.10's commit message
3.24.10

* FIX: correct `index.exportSynonyms` and `index.exportRules`
  * they had the wrong implementation until now
  * add some tests to prevent regression

3.24.9

Toggle 3.24.9's commit message
3.24.9

* FIX: make sure long API keys are sent via the POST body
  * this wasn't the case in 3.24.8 because of a typo

3.24.8

Toggle 3.24.8's commit message
3.24.8

* add multi cluster management methods
  * [ Assign or Move a userID to a cluster](https://algolia.com/doc/api-reference/api-methods/assign-user-id/): `assignUserID`
  * [Get userID with highest number of records per cluster](https://algolia.com/doc/api-reference/api-methods/get-top-user-id/): `getTopUserID`
  * [Returns the userID data stored in the mapping](https://algolia.com/doc/api-reference/api-methods/get-user-id/): `getUserID`
  * [List the clusters available in a multi-clusters setup for a single appID](https://algolia.com/doc/api-reference/api-methods/list-clusters/): `listClusters`
  * [List the userIDs assigned to a multi-clusters appID](https://algolia.com/doc/api-reference/api-methods/list-user-id/): `listUserIDs`
  * [Remove a userID and associated data from the multi-clusters](https://algolia.com/doc/api-reference/api-methods/remove-user-id/): `removeUserID`
  * [Search for userIDs](https://algolia.com/doc/api-reference/api-methods/search-user-id/): `searchUserIDs`