@algolia/recommend 5.9.1 → 5.10.0-beta.1

package/model/baseRecommendIndexSettings.ts

@@ -1,184 +0,0 @@
-// Code generated by OpenAPI Generator (https://openapi-generator.tech), manual changes will be lost - read more on https://github.com/algolia/api-clients-automation. DO NOT EDIT.
-
-import type { AdvancedSyntaxFeatures } from './advancedSyntaxFeatures';
-import type { AlternativesAsExact } from './alternativesAsExact';
-import type { Distinct } from './distinct';
-import type { ExactOnSingleWordQuery } from './exactOnSingleWordQuery';
-import type { IgnorePlurals } from './ignorePlurals';
-import type { QueryType } from './queryType';
-import type { ReRankingApplyFilter } from './reRankingApplyFilter';
-import type { RemoveStopWords } from './removeStopWords';
-import type { RemoveWordsIfNoResults } from './removeWordsIfNoResults';
-import type { RenderingContent } from './renderingContent';
-import type { SupportedLanguage } from './supportedLanguage';
-import type { TypoTolerance } from './typoTolerance';
-
-export type BaseRecommendIndexSettings = {
-  /**
-   * Attributes to include in the API response.  To reduce the size of your response, you can retrieve only some of the attributes. Attribute names are case-sensitive.  - `*` retrieves all attributes, except attributes included in the `customRanking` and `unretrievableAttributes` settings. - To retrieve all attributes except a specific one, prefix the attribute with a dash and combine it with the `*`: `[\"*\", \"-ATTRIBUTE\"]`. - The `objectID` attribute is always included.
-   */
-  attributesToRetrieve?: Array<string>;
-
-  /**
-   * Determines the order in which Algolia returns your results.  By default, each entry corresponds to a [ranking criteria](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/). The tie-breaking algorithm sequentially applies each criterion in the order they\'re specified. If you configure a replica index for [sorting by an attribute](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/how-to/sort-by-attribute/), you put the sorting attribute at the top of the list.  **Modifiers**  - `asc(\"ATTRIBUTE\")`.   Sort the index by the values of an attribute, in ascending order. - `desc(\"ATTRIBUTE\")`.   Sort the index by the values of an attribute, in descending order.  Before you modify the default setting, you should test your changes in the dashboard, and by [A/B testing](https://www.algolia.com/doc/guides/ab-testing/what-is-ab-testing/).
-   */
-  ranking?: Array<string>;
-
-  /**
-   * Relevancy threshold below which less relevant results aren\'t included in the results.  You can only set `relevancyStrictness` on [virtual replica indices](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/replicas/#what-are-virtual-replicas). Use this setting to strike a balance between the relevance and number of returned results.
-   */
-  relevancyStrictness?: number;
-
-  /**
-   * Attributes to highlight.  By default, all searchable attributes are highlighted. Use `*` to highlight all attributes or use an empty array `[]` to turn off highlighting. Attribute names are case-sensitive.  With highlighting, strings that match the search query are surrounded by HTML tags defined by `highlightPreTag` and `highlightPostTag`. You can use this to visually highlight matching parts of a search query in your UI.  For more information, see [Highlighting and snippeting](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/highlighting-snippeting/js/).
-   */
-  attributesToHighlight?: Array<string>;
-
-  /**
-   * Attributes for which to enable snippets. Attribute names are case-sensitive.  Snippets provide additional context to matched words. If you enable snippets, they include 10 words, including the matched word. The matched word will also be wrapped by HTML tags for highlighting. You can adjust the number of words with the following notation: `ATTRIBUTE:NUMBER`, where `NUMBER` is the number of words to be extracted.
-   */
-  attributesToSnippet?: Array<string>;
-
-  /**
-   * HTML tag to insert before the highlighted parts in all highlighted results and snippets.
-   */
-  highlightPreTag?: string;
-
-  /**
-   * HTML tag to insert after the highlighted parts in all highlighted results and snippets.
-   */
-  highlightPostTag?: string;
-
-  /**
-   * String used as an ellipsis indicator when a snippet is truncated.
-   */
-  snippetEllipsisText?: string;
-
-  /**
-   * Whether to restrict highlighting and snippeting to items that at least partially matched the search query. By default, all items are highlighted and snippeted.
-   */
-  restrictHighlightAndSnippetArrays?: boolean;
-
-  /**
-   * Minimum number of characters a word in the search query must contain to accept matches with [one typo](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/in-depth/configuring-typo-tolerance/#configuring-word-length-for-typos).
-   */
-  minWordSizefor1Typo?: number;
-
-  /**
-   * Minimum number of characters a word in the search query must contain to accept matches with [two typos](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/in-depth/configuring-typo-tolerance/#configuring-word-length-for-typos).
-   */
-  minWordSizefor2Typos?: number;
-
-  typoTolerance?: TypoTolerance;
-
-  /**
-   * Whether to allow typos on numbers in the search query.  Turn off this setting to reduce the number of irrelevant matches when searching in large sets of similar numbers.
-   */
-  allowTyposOnNumericTokens?: boolean;
-
-  /**
-   * Attributes for which you want to turn off [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/). Attribute names are case-sensitive.  Returning only exact matches can help when:  - [Searching in hyphenated attributes](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/how-to/how-to-search-in-hyphenated-attributes/). - Reducing the number of matches when you have too many.   This can happen with attributes that are long blocks of text, such as product descriptions.  Consider alternatives such as `disableTypoToleranceOnWords` or adding synonyms if your attributes have intentional unusual spellings that might look like typos.
-   */
-  disableTypoToleranceOnAttributes?: Array<string>;
-
-  ignorePlurals?: IgnorePlurals;
-
-  removeStopWords?: RemoveStopWords;
-
-  /**
-   * Languages for language-specific query processing steps such as plurals, stop-word removal, and word-detection dictionaries.  This setting sets a default list of languages used by the `removeStopWords` and `ignorePlurals` settings. This setting also sets a dictionary for word detection in the logogram-based [CJK](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/normalization/#normalization-for-logogram-based-languages-cjk) languages. To support this, you must place the CJK language **first**.  **You should always specify a query language.** If you don\'t specify an indexing language, the search engine uses all [supported languages](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages/), or the languages you specified with the `ignorePlurals` or `removeStopWords` parameters. This can lead to unexpected search results. For more information, see [Language-specific configuration](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/).
-   */
-  queryLanguages?: Array<SupportedLanguage>;
-
-  /**
-   * Whether to split compound words in the query into their building blocks.  For more information, see [Word segmentation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/#splitting-compound-words). Word segmentation is supported for these languages: German, Dutch, Finnish, Swedish, and Norwegian. Decompounding doesn\'t work for words with [non-spacing mark Unicode characters](https://www.charactercodes.net/category/non-spacing_mark). For example, `Gartenstühle` won\'t be decompounded if the `ü` consists of `u` (U+0075) and `◌̈` (U+0308).
-   */
-  decompoundQuery?: boolean;
-
-  /**
-   * Whether to enable rules.
-   */
-  enableRules?: boolean;
-
-  /**
-   * Whether to enable Personalization.
-   */
-  enablePersonalization?: boolean;
-
-  queryType?: QueryType;
-
-  removeWordsIfNoResults?: RemoveWordsIfNoResults;
-
-  /**
-   * Whether to support phrase matching and excluding words from search queries.  Use the `advancedSyntaxFeatures` parameter to control which feature is supported.
-   */
-  advancedSyntax?: boolean;
-
-  /**
-   * Words that should be considered optional when found in the query.  By default, records must match all words in the search query to be included in the search results. Adding optional words can help to increase the number of search results by running an additional search query that doesn\'t include the optional words. For example, if the search query is \"action video\" and \"video\" is an optional word, the search engine runs two queries. One for \"action video\" and one for \"action\". Records that match all words are ranked higher.  For a search query with 4 or more words **and** all its words are optional, the number of matched words required for a record to be included in the search results increases for every 1,000 records:  - If `optionalWords` has less than 10 words, the required number of matched words increases by 1:   results 1 to 1,000 require 1 matched word, results 1,001 to 2000 need 2 matched words. - If `optionalWords` has 10 or more words, the number of required matched words increases by the number of optional words divided by 5 (rounded down).   For example, with 18 optional words: results 1 to 1,000 require 1 matched word, results 1,001 to 2000 need 4 matched words.  For more information, see [Optional words](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/#creating-a-list-of-optional-words).
-   */
-  optionalWords?: Array<string>;
-
-  /**
-   * Searchable attributes for which you want to [turn off the Exact ranking criterion](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/in-depth/adjust-exact-settings/#turn-off-exact-for-some-attributes). Attribute names are case-sensitive.  This can be useful for attributes with long values, where the likelihood of an exact match is high, such as product descriptions. Turning off the Exact ranking criterion for these attributes favors exact matching on other attributes. This reduces the impact of individual attributes with a lot of content on ranking.
-   */
-  disableExactOnAttributes?: Array<string>;
-
-  exactOnSingleWordQuery?: ExactOnSingleWordQuery;
-
-  /**
-   * 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>;
-
-  /**
-   * Advanced search syntax features you want to support.  - `exactPhrase`.   Phrases in quotes must match exactly.   For example, `sparkly blue \"iPhone case\"` only returns records with the exact string \"iPhone case\".  - `excludeWords`.   Query words prefixed with a `-` must not occur in a record.   For example, `search -engine` matches records that contain \"search\" but not \"engine\".  This setting only has an effect if `advancedSyntax` is true.
-   */
-  advancedSyntaxFeatures?: Array<AdvancedSyntaxFeatures>;
-
-  distinct?: Distinct;
-
-  /**
-   * Whether to replace a highlighted word with the matched synonym.  By default, the original words are highlighted even if a synonym matches. For example, with `home` as a synonym for `house` and a search for `home`, records matching either \"home\" or \"house\" are included in the search results, and either \"home\" or \"house\" are highlighted.  With `replaceSynonymsInHighlight` set to `true`, a search for `home` still matches the same records, but all occurrences of \"house\" are replaced by \"home\" in the highlighted response.
-   */
-  replaceSynonymsInHighlight?: boolean;
-
-  /**
-   * Minimum proximity score for two matching words.  This adjusts the [Proximity ranking criterion](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#proximity) by equally scoring matches that are farther apart.  For example, if `minProximity` is 2, neighboring matches and matches with one word between them would have the same score.
-   */
-  minProximity?: number;
-
-  /**
-   * Properties to include in the API response of `search` and `browse` requests.  By default, all response properties are included. To reduce the response size, you can select, which attributes should be included.  You can\'t exclude these properties: `message`, `warning`, `cursor`, `serverUsed`, `indexUsed`, `abTestVariantID`, `parsedQuery`, or any property triggered by the `getRankingInfo` parameter.  Don\'t exclude properties that you might need in your search UI.
-   */
-  responseFields?: Array<string>;
-
-  /**
-   * Maximum number of facet values to return when [searching for facet values](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#search-for-facet-values).
-   */
-  maxFacetHits?: number;
-
-  /**
-   * Maximum number of facet values to return for each facet.
-   */
-  maxValuesPerFacet?: number;
-
-  /**
-   * Order in which to retrieve facet values.  - `count`.   Facet values are retrieved by decreasing count.   The count is the number of matching records containing this facet value.  - `alpha`.   Retrieve facet values alphabetically.  This setting doesn\'t influence how facet values are displayed in your UI (see `renderingContent`). For more information, see [facet value display](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/facet-display/js/).
-   */
-  sortFacetValuesBy?: string;
-
-  /**
-   * Whether the best matching attribute should be determined by minimum proximity.  This setting only affects ranking if the Attribute ranking criterion comes before Proximity in the `ranking` setting. If true, the best matching attribute is selected based on the minimum proximity of multiple matches. Otherwise, the best matching attribute is determined by the order in the `searchableAttributes` setting.
-   */
-  attributeCriteriaComputedByMinProximity?: boolean;
-
-  renderingContent?: RenderingContent;
-
-  /**
-   * Whether this search will use [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking/).  This setting only has an effect if you activated Dynamic Re-Ranking for this index in the Algolia dashboard.
-   */
-  enableReRanking?: boolean;
-
-  reRankingApplyFilter?: ReRankingApplyFilter | null;
-};

package/model/baseRecommendRequest.ts

@@ -1,22 +0,0 @@
-// Code generated by OpenAPI Generator (https://openapi-generator.tech), manual changes will be lost - read more on https://github.com/algolia/api-clients-automation. DO NOT EDIT.
-
-import type { RecommendSearchParams } from './recommendSearchParams';
-
-export type BaseRecommendRequest = {
-  /**
-   * Index name (case-sensitive).
-   */
-  indexName: string;
-
-  /**
-   * Minimum score a recommendation must have to be included in the response.
-   */
-  threshold: number;
-
-  /**
-   * Maximum number of recommendations to retrieve. By default, all recommendations are returned and no fallback request is made. Depending on the available recommendations and the other request parameters, the actual number of recommendations may be lower than this value.
-   */
-  maxRecommendations?: number;
-
-  queryParameters?: RecommendSearchParams;
-};

package/model/baseRecommendSearchParams.ts

@@ -1,133 +0,0 @@
-// Code generated by OpenAPI Generator (https://openapi-generator.tech), manual changes will be lost - read more on https://github.com/algolia/api-clients-automation. DO NOT EDIT.
-
-import type { AroundPrecision } from './aroundPrecision';
-import type { AroundRadius } from './aroundRadius';
-import type { FacetFilters } from './facetFilters';
-import type { NumericFilters } from './numericFilters';
-import type { OptionalFilters } from './optionalFilters';
-import type { SupportedLanguage } from './supportedLanguage';
-import type { TagFilters } from './tagFilters';
-
-export type BaseRecommendSearchParams = {
-  /**
-   * Keywords to be used instead of the search query to conduct a more broader search.  Using the `similarQuery` parameter changes other settings:  - `queryType` is set to `prefixNone`. - `removeStopWords` is set to true. - `words` is set as the first ranking criterion. - All remaining words are treated as `optionalWords`.  Since the `similarQuery` is supposed to do a broad search, they usually return many results. Combine it with `filters` to narrow down the list of results.
-   */
-  similarQuery?: string;
-
-  /**
-   * Filter expression to only include items that match the filter criteria in the response.  You can use these filter expressions:  - **Numeric filters.** `<facet> <op> <number>`, where `<op>` is one of `<`, `<=`, `=`, `!=`, `>`, `>=`. - **Ranges.** `<facet>:<lower> TO <upper>` where `<lower>` and `<upper>` are the lower and upper limits of the range (inclusive). - **Facet filters.** `<facet>:<value>` where `<facet>` is a facet attribute (case-sensitive) and `<value>` a facet value. - **Tag filters.** `_tags:<value>` or just `<value>` (case-sensitive). - **Boolean filters.** `<facet>: true | false`.  You can combine filters with `AND`, `OR`, and `NOT` operators with the following restrictions:  - You can only combine filters of the same type with `OR`.   **Not supported:** `facet:value OR num > 3`. - You can\'t use `NOT` with combinations of filters.   **Not supported:** `NOT(facet:value OR facet:value)` - You can\'t combine conjunctions (`AND`) with `OR`.   **Not supported:** `facet:value OR (facet:value AND facet:value)`  Use quotes around your filters, if the facet attribute name or facet value has spaces, keywords (`OR`, `AND`, `NOT`), or quotes. If a facet attribute is an array, the filter matches if it matches at least one element of the array.  For more information, see [Filters](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering/).
-   */
-  filters?: string;
-
-  facetFilters?: FacetFilters;
-
-  optionalFilters?: OptionalFilters;
-
-  numericFilters?: NumericFilters;
-
-  tagFilters?: TagFilters;
-
-  /**
-   * Whether to sum all filter scores.  If true, all filter scores are summed. Otherwise, the maximum filter score is kept. For more information, see [filter scores](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering/in-depth/filter-scoring/#accumulating-scores-with-sumorfiltersscores).
-   */
-  sumOrFiltersScores?: boolean;
-
-  /**
-   * Restricts a search to a subset of your searchable attributes. Attribute names are case-sensitive.
-   */
-  restrictSearchableAttributes?: Array<string>;
-
-  /**
-   * Facets for which to retrieve facet values that match the search criteria and the number of matching facet values.  To retrieve all facets, use the wildcard character `*`. For more information, see [facets](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#contextual-facet-values-and-counts).
-   */
-  facets?: Array<string>;
-
-  /**
-   * Whether faceting should be applied after deduplication with `distinct`.  This leads to accurate facet counts when using faceting in combination with `distinct`. It\'s usually better to use `afterDistinct` modifiers in the `attributesForFaceting` setting, as `facetingAfterDistinct` only computes correct facet counts if all records have the same facet values for the `attributeForDistinct`.
-   */
-  facetingAfterDistinct?: boolean;
-
-  /**
-   * Coordinates for the center of a circle, expressed as a comma-separated string of latitude and longitude.  Only records included within a circle around this central location are included in the results. The radius of the circle is determined by the `aroundRadius` and `minimumAroundRadius` settings. This parameter is ignored if you also specify `insidePolygon` or `insideBoundingBox`.
-   */
-  aroundLatLng?: string;
-
-  /**
-   * Whether to obtain the coordinates from the request\'s IP address.
-   */
-  aroundLatLngViaIP?: boolean;
-
-  aroundRadius?: AroundRadius;
-
-  aroundPrecision?: AroundPrecision;
-
-  /**
-   * Minimum radius (in meters) for a search around a location when `aroundRadius` isn\'t set.
-   */
-  minimumAroundRadius?: number;
-
-  /**
-   * Coordinates for a rectangular area in which to search.  Each bounding box is defined by the two opposite points of its diagonal, and expressed as latitude and longitude pair: `[p1 lat, p1 long, p2 lat, p2 long]`. Provide multiple bounding boxes as nested arrays. For more information, see [rectangular area](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas).
-   */
-  insideBoundingBox?: Array<Array<number>>;
-
-  /**
-   * Coordinates of a polygon in which to search.  Polygons are defined by 3 to 10,000 points. Each point is represented by its latitude and longitude. Provide multiple polygons as nested arrays. For more information, see [filtering inside polygons](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas). This parameter is ignored if you also specify `insideBoundingBox`.
-   */
-  insidePolygon?: Array<Array<number>>;
-
-  /**
-   * ISO language codes that adjust settings that are useful for processing natural language queries (as opposed to keyword searches):  - Sets `removeStopWords` and `ignorePlurals` to the list of provided languages. - Sets `removeWordsIfNoResults` to `allOptional`. - Adds a `natural_language` attribute to `ruleContexts` and `analyticsTags`.
-   */
-  naturalLanguages?: Array<SupportedLanguage>;
-
-  /**
-   * Assigns a rule context to the search query.  [Rule contexts](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/how-to/customize-search-results-by-platform/#whats-a-context) are strings that you can use to trigger matching rules.
-   */
-  ruleContexts?: Array<string>;
-
-  /**
-   * Impact that Personalization should have on this search.  The higher this value is, the more Personalization determines the ranking compared to other factors. For more information, see [Understanding Personalization impact](https://www.algolia.com/doc/guides/personalization/personalizing-results/in-depth/configuring-personalization/#understanding-personalization-impact).
-   */
-  personalizationImpact?: number;
-
-  /**
-   * Unique pseudonymous or anonymous user identifier.  This helps with analytics and click and conversion events. For more information, see [user token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken/).
-   */
-  userToken?: string;
-
-  /**
-   * Whether the search response should include detailed ranking information.
-   */
-  getRankingInfo?: boolean;
-
-  /**
-   * Whether to take into account an index\'s synonyms for this search.
-   */
-  synonyms?: boolean;
-
-  /**
-   * Whether to include a `queryID` attribute in the response.  The query ID is a unique identifier for a search query and is required for tracking [click and conversion events](https://www.algolia.com/guides/sending-events/getting-started/).
-   */
-  clickAnalytics?: boolean;
-
-  /**
-   * Whether this search will be included in Analytics.
-   */
-  analytics?: boolean;
-
-  /**
-   * Tags to apply to the query for [segmenting analytics data](https://www.algolia.com/doc/guides/search-analytics/guides/segments/).
-   */
-  analyticsTags?: Array<string>;
-
-  /**
-   * Whether to include this search when calculating processing-time percentiles.
-   */
-  percentileComputation?: boolean;
-
-  /**
-   * Whether to enable A/B testing for this search.
-   */
-  enableABTest?: boolean;
-};

package/model/baseSearchResponse.ts

@@ -1,129 +0,0 @@
-// Code generated by OpenAPI Generator (https://openapi-generator.tech), manual changes will be lost - read more on https://github.com/algolia/api-clients-automation. DO NOT EDIT.
-
-import type { Exhaustive } from './exhaustive';
-import type { FacetStats } from './facetStats';
-import type { Redirect } from './redirect';
-import type { RenderingContent } from './renderingContent';
-
-export type BaseSearchResponse = Record<string, any> & {
-  /**
-   * A/B test ID. This is only included in the response for indices that are part of an A/B test.
-   */
-  abTestID?: number;
-
-  /**
-   * Variant ID. This is only included in the response for indices that are part of an A/B test.
-   */
-  abTestVariantID?: number;
-
-  /**
-   * Computed geographical location.
-   */
-  aroundLatLng?: string;
-
-  /**
-   * Distance from a central coordinate provided by `aroundLatLng`.
-   */
-  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.
-   */
-  exhaustiveFacetsCount?: boolean;
-
-  /**
-   * See the `nbHits` field of the `exhaustive` object in the response.
-   */
-  exhaustiveNbHits?: boolean;
-
-  /**
-   * See the `typo` field of the `exhaustive` object in the response.
-   */
-  exhaustiveTypo?: boolean;
-
-  /**
-   * Facet counts.
-   */
-  facets?: { [key: string]: { [key: string]: number } };
-
-  /**
-   * Statistics for numerical facets.
-   */
-  facets_stats?: { [key: string]: FacetStats };
-
-  /**
-   * Index name used for the query.
-   */
-  index?: string;
-
-  /**
-   * Index name used for the query. During A/B testing, the targeted index isn\'t always the index used by the query.
-   */
-  indexUsed?: string;
-
-  /**
-   * Warnings about the query.
-   */
-  message?: string;
-
-  /**
-   * Number of hits selected and sorted by the relevant sort algorithm.
-   */
-  nbSortedHits?: number;
-
-  /**
-   * Post-[normalization](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/#what-does-normalization-mean) query string that will be searched.
-   */
-  parsedQuery?: string;
-
-  /**
-   * Time the server took to process the request, in milliseconds.
-   */
-  processingTimeMS: number;
-
-  /**
-   * Experimental. List of processing steps and their times, in milliseconds. You can use this list to investigate performance issues.
-   */
-  processingTimingsMS?: Record<string, unknown>;
-
-  /**
-   * Markup text indicating which parts of the original query have been removed to retrieve a non-empty result set.
-   */
-  queryAfterRemoval?: string;
-
-  redirect?: Redirect;
-
-  renderingContent?: RenderingContent;
-
-  /**
-   * Time the server took to process the request, in milliseconds.
-   */
-  serverTimeMS?: number;
-
-  /**
-   * Host name of the server that processed the request.
-   */
-  serverUsed?: string;
-
-  /**
-   * An object with custom data.  You can store up to 32kB as custom data.
-   */
-  userData?: Record<string, unknown>;
-
-  /**
-   * Unique identifier for the query. This is used for [click analytics](https://www.algolia.com/doc/guides/analytics/click-analytics/).
-   */
-  queryID?: string;
-
-  /**
-   * Whether automatic events collection is enabled for the application.
-   */
-  _automaticInsights?: boolean;
-};

package/model/booleanString.ts

@@ -1,3 +0,0 @@
-// Code generated by OpenAPI Generator (https://openapi-generator.tech), manual changes will be lost - read more on https://github.com/algolia/api-clients-automation. DO NOT EDIT.
-
-export type BooleanString = 'true' | 'false';

package/model/boughtTogetherQuery.ts

@@ -1,6 +0,0 @@
-// Code generated by OpenAPI Generator (https://openapi-generator.tech), manual changes will be lost - read more on https://github.com/algolia/api-clients-automation. DO NOT EDIT.
-
-import type { BaseRecommendRequest } from './baseRecommendRequest';
-import type { FrequentlyBoughtTogether } from './frequentlyBoughtTogether';
-
-export type BoughtTogetherQuery = BaseRecommendRequest & FrequentlyBoughtTogether;

package/model/clientMethodProps.ts

@@ -1,163 +0,0 @@
-// Code generated by OpenAPI Generator (https://openapi-generator.tech), manual changes will be lost - read more on https://github.com/algolia/api-clients-automation. DO NOT EDIT.
-
-import { RecommendModels } from '../model/recommendModels';
-import { RecommendRule } from '../model/recommendRule';
-
-import { SearchRecommendRulesParams } from '../model/searchRecommendRulesParams';
-
-import type { RecommendationsRequest } from './recommendationsRequest';
-
-/**
- * Properties for the `batchRecommendRules` method.
- */
-export type BatchRecommendRulesProps = {
-  /**
-   * Name of the index on which to perform the operation.
-   */
-  indexName: string;
-  /**
-   * [Recommend model](https://www.algolia.com/doc/guides/algolia-recommend/overview/#recommend-models).
-   */
-  model: RecommendModels;
-  recommendRule?: Array<RecommendRule>;
-};
-
-/**
- * Properties for the `customDelete` method.
- */
-export type CustomDeleteProps = {
-  /**
-   * Path of the endpoint, anything after \"/1\" must be specified.
-   */
-  path: string;
-  /**
-   * Query parameters to apply to the current query.
-   */
-  parameters?: { [key: string]: any };
-};
-
-/**
- * Properties for the `customGet` method.
- */
-export type CustomGetProps = {
-  /**
-   * Path of the endpoint, anything after \"/1\" must be specified.
-   */
-  path: string;
-  /**
-   * Query parameters to apply to the current query.
-   */
-  parameters?: { [key: string]: any };
-};
-
-/**
- * Properties for the `customPost` method.
- */
-export type CustomPostProps = {
-  /**
-   * Path of the endpoint, anything after \"/1\" must be specified.
-   */
-  path: string;
-  /**
-   * Query parameters to apply to the current query.
-   */
-  parameters?: { [key: string]: any };
-  /**
-   * Parameters to send with the custom request.
-   */
-  body?: Record<string, unknown>;
-};
-
-/**
- * Properties for the `customPut` method.
- */
-export type CustomPutProps = {
-  /**
-   * Path of the endpoint, anything after \"/1\" must be specified.
-   */
-  path: string;
-  /**
-   * Query parameters to apply to the current query.
-   */
-  parameters?: { [key: string]: any };
-  /**
-   * Parameters to send with the custom request.
-   */
-  body?: Record<string, unknown>;
-};
-
-/**
- * Properties for the `deleteRecommendRule` method.
- */
-export type DeleteRecommendRuleProps = {
-  /**
-   * Name of the index on which to perform the operation.
-   */
-  indexName: string;
-  /**
-   * [Recommend model](https://www.algolia.com/doc/guides/algolia-recommend/overview/#recommend-models).
-   */
-  model: RecommendModels;
-  /**
-   * Unique record identifier.
-   */
-  objectID: string;
-};
-
-/**
- * Properties for the `getRecommendRule` method.
- */
-export type GetRecommendRuleProps = {
-  /**
-   * Name of the index on which to perform the operation.
-   */
-  indexName: string;
-  /**
-   * [Recommend model](https://www.algolia.com/doc/guides/algolia-recommend/overview/#recommend-models).
-   */
-  model: RecommendModels;
-  /**
-   * Unique record identifier.
-   */
-  objectID: string;
-};
-
-/**
- * Properties for the `getRecommendStatus` method.
- */
-export type GetRecommendStatusProps = {
-  /**
-   * Name of the index on which to perform the operation.
-   */
-  indexName: string;
-  /**
-   * [Recommend model](https://www.algolia.com/doc/guides/algolia-recommend/overview/#recommend-models).
-   */
-  model: RecommendModels;
-  /**
-   * Unique task identifier.
-   */
-  taskID: number;
-};
-
-/**
- * Recommend method signature compatible with the `algoliasearch` v4 package. When using this signature, extra computation will be required to make it match the new signature.
- *
- * @deprecated This signature will be removed from the next major version, we recommend using the `GetRecommendationsParams` type for performances and future proof reasons.
- */
-export type LegacyGetRecommendationsParams = RecommendationsRequest[];
-
-/**
- * Properties for the `searchRecommendRules` method.
- */
-export type SearchRecommendRulesProps = {
-  /**
-   * Name of the index on which to perform the operation.
-   */
-  indexName: string;
-  /**
-   * [Recommend model](https://www.algolia.com/doc/guides/algolia-recommend/overview/#recommend-models).
-   */
-  model: RecommendModels;
-  searchRecommendRulesParams?: SearchRecommendRulesParams;
-};