@algolia/client-search 5.8.1 → 5.9.0

package/dist/fetch.d.ts

@@ -283,6 +283,10 @@ type BaseSearchResponse = Record<string, any> & {
      */
     automaticRadius?: string;
     exhaustive?: Exhaustive;
+    /**
+     * Rules applied to the query.
+     */
+    appliedRules?: Array<Record<string, unknown>>;
     /**
      * See the `facetsCount` field of the `exhaustive` object in the response.
      */
@@ -630,7 +634,7 @@ type BaseGetApiKeyResponse = {
     /**
      * API key.
      */
-    value?: string;
+    value: string;
     /**
      * Timestamp when the object was created, in milliseconds since the Unix epoch.
      */
@@ -754,7 +758,7 @@ type GetObjectsResponse<T = Record<string, any>> = {
     /**
      * Retrieved records.
      */
-    results: T[];
+    results?: T[];
 };
 
 /**
@@ -1337,7 +1341,7 @@ type IndexSettingsAsSearchParams = {
     disableExactOnAttributes?: Array<string>;
     exactOnSingleWordQuery?: ExactOnSingleWordQuery;
     /**
-     * Alternatives of query words that should be considered as exact matches by the Exact ranking criterion.  - `ignorePlurals`.   Plurals and similar declensions added by the `ignorePlurals` setting are considered exact matches.  - `singleWordSynonym`.   Single-word synonyms, such as \"NY/NYC\" are considered exact matches.  - `multiWordsSynonym`.   Multi-word synonyms, such as \"NY/New York\" are considered exact matches.
+     * Determine which plurals and synonyms should be considered an exact matches.  By default, Algolia treats singular and plural forms of a word, and single-word synonyms, as [exact](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#exact) matches when searching. For example:  - \"swimsuit\" and \"swimsuits\" are treated the same - \"swimsuit\" and \"swimwear\" are treated the same (if they are [synonyms](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/adding-synonyms/#regular-synonyms)).  - `ignorePlurals`.   Plurals and similar declensions added by the `ignorePlurals` setting are considered exact matches.  - `singleWordSynonym`.   Single-word synonyms, such as \"NY\" = \"NYC\", are considered exact matches.  - `multiWordsSynonym`.   Multi-word synonyms, such as \"NY\" = \"New York\", are considered exact matches.
      */
     alternativesAsExact?: Array<AlternativesAsExact>;
     /**
@@ -1611,7 +1615,7 @@ type SearchDictionaryEntriesResponse = {
      */
     hits: Array<DictionaryEntry>;
     /**
-     * Requested page of the API response.
+     * Requested page of the API response.  Algolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/)).  - `hitsPerPage`: sets the number of search results (_hits_) displayed per page. - `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.  For example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.
      */
     page: number;
     /**
@@ -1903,7 +1907,7 @@ type SearchUserIdsResponse = {
      */
     page: number;
     /**
-     * Maximum number of hits per page.
+     * Maximum number of hits per page.  Algolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/)).  - `hitsPerPage`: sets the number of search results (_hits_) displayed per page. - `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.  For example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.
      */
     hitsPerPage: number;
     /**
@@ -1930,7 +1934,7 @@ type BaseIndexSettings = {
      */
     unretrievableAttributes?: Array<string>;
     /**
-     * Words for which you want to turn off [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/). This also turns off [word splitting and concatenation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/splitting-and-concatenation/) for the specified words.
+     * Creates a list of [words which require exact matches](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/in-depth/configuring-typo-tolerance/#turn-off-typo-tolerance-for-certain-words). This also turns off [word splitting and concatenation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/splitting-and-concatenation/) for the specified words.
      */
     disableTypoToleranceOnWords?: Array<string>;
     /**
@@ -1962,7 +1966,7 @@ type BaseIndexSettings = {
      */
     numericAttributesForFiltering?: Array<string>;
     /**
-     * Controls which separators are indexed.  Separators are all non-letter characters except spaces and currency characters, such as $€£¥. By default, separator characters aren\'t indexed. With `separatorsToIndex`, Algolia treats separator characters as separate words. For example, a search for `C#` would report two matches.
+     * Control which non-alphanumeric characters are indexed.  By default, Algolia ignores [non-alphanumeric characters](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/how-to/how-to-search-in-hyphenated-attributes/#handling-non-alphanumeric-characters) like hyphen (`-`), plus (`+`), and parentheses (`(`,`)`). To include such characters, define them with `separatorsToIndex`.  Separators are all non-letter characters except spaces and currency characters, such as $€£¥.  With `separatorsToIndex`, Algolia treats separator characters as separate words. For example, in a search for \"Disney+\", Algolia considers \"Disney\" and \"+\" as two separate words.
      */
     separatorsToIndex?: string;
     /**
@@ -2222,11 +2226,11 @@ type SearchRulesParams = {
      */
     context?: string;
     /**
-     * Requested page of the API response.
+     * Requested page of the API response.  Algolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/)).  - `hitsPerPage`: sets the number of search results (_hits_) displayed per page. - `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.  For example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.
      */
     page?: number;
     /**
-     * Maximum number of hits per page.
+     * Maximum number of hits per page.  Algolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/)).  - `hitsPerPage`: sets the number of search results (_hits_) displayed per page. - `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.  For example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.
      */
     hitsPerPage?: number;
     /**
@@ -3033,7 +3037,7 @@ type ReplaceAllObjectsOptions = {
     batchSize?: number;
 };
 
-declare const apiClientVersion = "5.8.1";
+declare const apiClientVersion = "5.9.0";
 declare function createSearchClient({ appId: appIdOption, apiKey: apiKeyOption, authMode, algoliaAgents, ...options }: CreateClientOptions): {
     transporter: _algolia_client_common.Transporter;
     /**

package/dist/node.d.cts

@@ -283,6 +283,10 @@ type BaseSearchResponse = Record<string, any> & {
      */
     automaticRadius?: string;
     exhaustive?: Exhaustive;
+    /**
+     * Rules applied to the query.
+     */
+    appliedRules?: Array<Record<string, unknown>>;
     /**
      * See the `facetsCount` field of the `exhaustive` object in the response.
      */
@@ -630,7 +634,7 @@ type BaseGetApiKeyResponse = {
     /**
      * API key.
      */
-    value?: string;
+    value: string;
     /**
      * Timestamp when the object was created, in milliseconds since the Unix epoch.
      */
@@ -754,7 +758,7 @@ type GetObjectsResponse<T = Record<string, any>> = {
     /**
      * Retrieved records.
      */
-    results: T[];
+    results?: T[];
 };
 
 /**
@@ -1337,7 +1341,7 @@ type IndexSettingsAsSearchParams = {
     disableExactOnAttributes?: Array<string>;
     exactOnSingleWordQuery?: ExactOnSingleWordQuery;
     /**
-     * Alternatives of query words that should be considered as exact matches by the Exact ranking criterion.  - `ignorePlurals`.   Plurals and similar declensions added by the `ignorePlurals` setting are considered exact matches.  - `singleWordSynonym`.   Single-word synonyms, such as \"NY/NYC\" are considered exact matches.  - `multiWordsSynonym`.   Multi-word synonyms, such as \"NY/New York\" are considered exact matches.
+     * Determine which plurals and synonyms should be considered an exact matches.  By default, Algolia treats singular and plural forms of a word, and single-word synonyms, as [exact](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#exact) matches when searching. For example:  - \"swimsuit\" and \"swimsuits\" are treated the same - \"swimsuit\" and \"swimwear\" are treated the same (if they are [synonyms](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/adding-synonyms/#regular-synonyms)).  - `ignorePlurals`.   Plurals and similar declensions added by the `ignorePlurals` setting are considered exact matches.  - `singleWordSynonym`.   Single-word synonyms, such as \"NY\" = \"NYC\", are considered exact matches.  - `multiWordsSynonym`.   Multi-word synonyms, such as \"NY\" = \"New York\", are considered exact matches.
      */
     alternativesAsExact?: Array<AlternativesAsExact>;
     /**
@@ -1611,7 +1615,7 @@ type SearchDictionaryEntriesResponse = {
      */
     hits: Array<DictionaryEntry>;
     /**
-     * Requested page of the API response.
+     * Requested page of the API response.  Algolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/)).  - `hitsPerPage`: sets the number of search results (_hits_) displayed per page. - `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.  For example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.
      */
     page: number;
     /**
@@ -1903,7 +1907,7 @@ type SearchUserIdsResponse = {
      */
     page: number;
     /**
-     * Maximum number of hits per page.
+     * Maximum number of hits per page.  Algolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/)).  - `hitsPerPage`: sets the number of search results (_hits_) displayed per page. - `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.  For example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.
      */
     hitsPerPage: number;
     /**
@@ -1930,7 +1934,7 @@ type BaseIndexSettings = {
      */
     unretrievableAttributes?: Array<string>;
     /**
-     * Words for which you want to turn off [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/). This also turns off [word splitting and concatenation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/splitting-and-concatenation/) for the specified words.
+     * Creates a list of [words which require exact matches](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/in-depth/configuring-typo-tolerance/#turn-off-typo-tolerance-for-certain-words). This also turns off [word splitting and concatenation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/splitting-and-concatenation/) for the specified words.
      */
     disableTypoToleranceOnWords?: Array<string>;
     /**
@@ -1962,7 +1966,7 @@ type BaseIndexSettings = {
      */
     numericAttributesForFiltering?: Array<string>;
     /**
-     * Controls which separators are indexed.  Separators are all non-letter characters except spaces and currency characters, such as $€£¥. By default, separator characters aren\'t indexed. With `separatorsToIndex`, Algolia treats separator characters as separate words. For example, a search for `C#` would report two matches.
+     * Control which non-alphanumeric characters are indexed.  By default, Algolia ignores [non-alphanumeric characters](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/how-to/how-to-search-in-hyphenated-attributes/#handling-non-alphanumeric-characters) like hyphen (`-`), plus (`+`), and parentheses (`(`,`)`). To include such characters, define them with `separatorsToIndex`.  Separators are all non-letter characters except spaces and currency characters, such as $€£¥.  With `separatorsToIndex`, Algolia treats separator characters as separate words. For example, in a search for \"Disney+\", Algolia considers \"Disney\" and \"+\" as two separate words.
      */
     separatorsToIndex?: string;
     /**
@@ -2222,11 +2226,11 @@ type SearchRulesParams = {
      */
     context?: string;
     /**
-     * Requested page of the API response.
+     * Requested page of the API response.  Algolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/)).  - `hitsPerPage`: sets the number of search results (_hits_) displayed per page. - `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.  For example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.
      */
     page?: number;
     /**
-     * Maximum number of hits per page.
+     * Maximum number of hits per page.  Algolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/)).  - `hitsPerPage`: sets the number of search results (_hits_) displayed per page. - `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.  For example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.
      */
     hitsPerPage?: number;
     /**
@@ -3033,7 +3037,7 @@ type ReplaceAllObjectsOptions = {
     batchSize?: number;
 };
 
-declare const apiClientVersion = "5.8.1";
+declare const apiClientVersion = "5.9.0";
 declare function createSearchClient({ appId: appIdOption, apiKey: apiKeyOption, authMode, algoliaAgents, ...options }: CreateClientOptions): {
     transporter: _algolia_client_common.Transporter;
     /**

package/dist/node.d.ts

@@ -283,6 +283,10 @@ type BaseSearchResponse = Record<string, any> & {
      */
     automaticRadius?: string;
     exhaustive?: Exhaustive;
+    /**
+     * Rules applied to the query.
+     */
+    appliedRules?: Array<Record<string, unknown>>;
     /**
      * See the `facetsCount` field of the `exhaustive` object in the response.
      */
@@ -630,7 +634,7 @@ type BaseGetApiKeyResponse = {
     /**
      * API key.
      */
-    value?: string;
+    value: string;
     /**
      * Timestamp when the object was created, in milliseconds since the Unix epoch.
      */
@@ -754,7 +758,7 @@ type GetObjectsResponse<T = Record<string, any>> = {
     /**
      * Retrieved records.
      */
-    results: T[];
+    results?: T[];
 };
 
 /**
@@ -1337,7 +1341,7 @@ type IndexSettingsAsSearchParams = {
     disableExactOnAttributes?: Array<string>;
     exactOnSingleWordQuery?: ExactOnSingleWordQuery;
     /**
-     * Alternatives of query words that should be considered as exact matches by the Exact ranking criterion.  - `ignorePlurals`.   Plurals and similar declensions added by the `ignorePlurals` setting are considered exact matches.  - `singleWordSynonym`.   Single-word synonyms, such as \"NY/NYC\" are considered exact matches.  - `multiWordsSynonym`.   Multi-word synonyms, such as \"NY/New York\" are considered exact matches.
+     * Determine which plurals and synonyms should be considered an exact matches.  By default, Algolia treats singular and plural forms of a word, and single-word synonyms, as [exact](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#exact) matches when searching. For example:  - \"swimsuit\" and \"swimsuits\" are treated the same - \"swimsuit\" and \"swimwear\" are treated the same (if they are [synonyms](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/adding-synonyms/#regular-synonyms)).  - `ignorePlurals`.   Plurals and similar declensions added by the `ignorePlurals` setting are considered exact matches.  - `singleWordSynonym`.   Single-word synonyms, such as \"NY\" = \"NYC\", are considered exact matches.  - `multiWordsSynonym`.   Multi-word synonyms, such as \"NY\" = \"New York\", are considered exact matches.
      */
     alternativesAsExact?: Array<AlternativesAsExact>;
     /**
@@ -1611,7 +1615,7 @@ type SearchDictionaryEntriesResponse = {
      */
     hits: Array<DictionaryEntry>;
     /**
-     * Requested page of the API response.
+     * Requested page of the API response.  Algolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/)).  - `hitsPerPage`: sets the number of search results (_hits_) displayed per page. - `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.  For example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.
      */
     page: number;
     /**
@@ -1903,7 +1907,7 @@ type SearchUserIdsResponse = {
      */
     page: number;
     /**
-     * Maximum number of hits per page.
+     * Maximum number of hits per page.  Algolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/)).  - `hitsPerPage`: sets the number of search results (_hits_) displayed per page. - `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.  For example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.
      */
     hitsPerPage: number;
     /**
@@ -1930,7 +1934,7 @@ type BaseIndexSettings = {
      */
     unretrievableAttributes?: Array<string>;
     /**
-     * Words for which you want to turn off [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/). This also turns off [word splitting and concatenation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/splitting-and-concatenation/) for the specified words.
+     * Creates a list of [words which require exact matches](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/in-depth/configuring-typo-tolerance/#turn-off-typo-tolerance-for-certain-words). This also turns off [word splitting and concatenation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/splitting-and-concatenation/) for the specified words.
      */
     disableTypoToleranceOnWords?: Array<string>;
     /**
@@ -1962,7 +1966,7 @@ type BaseIndexSettings = {
      */
     numericAttributesForFiltering?: Array<string>;
     /**
-     * Controls which separators are indexed.  Separators are all non-letter characters except spaces and currency characters, such as $€£¥. By default, separator characters aren\'t indexed. With `separatorsToIndex`, Algolia treats separator characters as separate words. For example, a search for `C#` would report two matches.
+     * Control which non-alphanumeric characters are indexed.  By default, Algolia ignores [non-alphanumeric characters](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/how-to/how-to-search-in-hyphenated-attributes/#handling-non-alphanumeric-characters) like hyphen (`-`), plus (`+`), and parentheses (`(`,`)`). To include such characters, define them with `separatorsToIndex`.  Separators are all non-letter characters except spaces and currency characters, such as $€£¥.  With `separatorsToIndex`, Algolia treats separator characters as separate words. For example, in a search for \"Disney+\", Algolia considers \"Disney\" and \"+\" as two separate words.
      */
     separatorsToIndex?: string;
     /**
@@ -2222,11 +2226,11 @@ type SearchRulesParams = {
      */
     context?: string;
     /**
-     * Requested page of the API response.
+     * Requested page of the API response.  Algolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/)).  - `hitsPerPage`: sets the number of search results (_hits_) displayed per page. - `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.  For example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.
      */
     page?: number;
     /**
-     * Maximum number of hits per page.
+     * Maximum number of hits per page.  Algolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/)).  - `hitsPerPage`: sets the number of search results (_hits_) displayed per page. - `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.  For example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.
      */
     hitsPerPage?: number;
     /**
@@ -3033,7 +3037,7 @@ type ReplaceAllObjectsOptions = {
     batchSize?: number;
 };
 
-declare const apiClientVersion = "5.8.1";
+declare const apiClientVersion = "5.9.0";
 declare function createSearchClient({ appId: appIdOption, apiKey: apiKeyOption, authMode, algoliaAgents, ...options }: CreateClientOptions): {
     transporter: _algolia_client_common.Transporter;
     /**

package/dist/src/searchClient.cjs

@@ -25,7 +25,7 @@ __export(searchClient_exports, {
 });
 module.exports = __toCommonJS(searchClient_exports);
 var import_client_common = require("@algolia/client-common");
-var apiClientVersion = "5.8.1";
+var apiClientVersion = "5.9.0";
 function getDefaultHosts(appId) {
   return [
     {