diff --git a/packages/algoliasearch/lite/model/acl.ts b/packages/algoliasearch/lite/model/acl.ts index c3522561e..d7413dac1 100644 --- a/packages/algoliasearch/lite/model/acl.ts +++ b/packages/algoliasearch/lite/model/acl.ts @@ -1,7 +1,7 @@ // 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. /** - * API key permissions: `addObject`: required to add or update records, copy or move an index. `analytics`: required to access the Analytics API. `browse`: required to view records `deleteIndex`: required to delete indices. `deleteObject`: required to delete records. `editSettings`: required to change index settings. `inference`: required to access the Inference API. `listIndexes`: required to list indices. `logs`: required to access logs of search and indexing operations. `recommendation`: required to access the Personalization and Recommend APIs. `search`: required to search records `seeUnretrievableAttributes`: required to retrieve [`unretrievableAttributes`](https://www.algolia.com/doc/api-reference/api-parameters/unretrievableAttributes/) for all operations that return records. `settings`: required to examine index settings. + * Access control list permissions. */ export type Acl = | 'addObject' diff --git a/packages/algoliasearch/lite/model/action.ts b/packages/algoliasearch/lite/model/action.ts index 339db6126..dd3583e54 100644 --- a/packages/algoliasearch/lite/model/action.ts +++ b/packages/algoliasearch/lite/model/action.ts @@ -1,7 +1,7 @@ // 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. /** - * Type of batch operation. + * Type of indexing operation. */ export type Action = | 'addObject' diff --git a/packages/algoliasearch/lite/model/addApiKeyResponse.ts b/packages/algoliasearch/lite/model/addApiKeyResponse.ts index 3817c9691..9f57140d0 100644 --- a/packages/algoliasearch/lite/model/addApiKeyResponse.ts +++ b/packages/algoliasearch/lite/model/addApiKeyResponse.ts @@ -7,7 +7,7 @@ export type AddApiKeyResponse = { key: string; /** - * Timestamp of creation in [ISO-8601](https://wikipedia.org/wiki/ISO_8601) format. + * Timestamp of creation in [ISO 8601](https://wikipedia.org/wiki/ISO_8601) format. */ createdAt: string; }; diff --git a/packages/algoliasearch/lite/model/anchoring.ts b/packages/algoliasearch/lite/model/anchoring.ts index c77a11939..cb727242e 100644 --- a/packages/algoliasearch/lite/model/anchoring.ts +++ b/packages/algoliasearch/lite/model/anchoring.ts @@ -1,6 +1,6 @@ // 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. /** - * Whether the pattern parameter matches the beginning (`startsWith`) or end (`endsWith`) of the query string, is an exact match (`is`), or a partial match (`contains`). + * Which part of the search query the pattern should match: - `startsWith`. The pattern must match the begginning of the query. - `endsWith`. The pattern must match the end of the query. - `is`. The pattern must match the query exactly. - `contains`. The pattern must match anywhere in the query. Empty queries are only allowed as pattern with `anchoring: is`. */ export type Anchoring = 'contains' | 'endsWith' | 'is' | 'startsWith'; diff --git a/packages/algoliasearch/lite/model/apiKey.ts b/packages/algoliasearch/lite/model/apiKey.ts index f30f69756..665d39c57 100644 --- a/packages/algoliasearch/lite/model/apiKey.ts +++ b/packages/algoliasearch/lite/model/apiKey.ts @@ -7,42 +7,42 @@ import type { Acl } from './acl'; */ export type ApiKey = { /** - * [Permissions](https://www.algolia.com/doc/guides/security/api-keys/#access-control-list-acl) associated with the key. + * Permissions that determine the type of API requests this key can make. The required ACL is listed in each endpoint\'s reference. For more information, see [access control list](https://www.algolia.com/doc/guides/security/api-keys/#access-control-list-acl). */ acl: Acl[]; /** - * Description of an API key for you and your team members. + * Description of an API key to help you identify this API key. */ description?: string; /** - * Restricts this API key to a list of indices or index patterns. If the list is empty, all indices are allowed. Specify either an exact index name or a pattern with a leading or trailing wildcard character (or both). For example: - `dev_*` matches all indices starting with \"dev_\" - `*_dev` matches all indices ending with \"_dev\" - `*_products_*` matches all indices containing \"_products_\". + * Index names or patterns that this API key can access. By default, an API key can access all indices in the same application. You can use leading and trailing wildcard characters (`*`): - `dev_*` matches all indices starting with \"dev_\". - `*_dev` matches all indices ending with \"_dev\". - `*_products_*` matches all indices containing \"_products_\". */ indexes?: string[]; /** - * Maximum number of hits this API key can retrieve in one query. If zero, no limit is enforced. > **Note**: Use this parameter to protect you from third-party attempts to retrieve your entire content by massively querying the index. + * Maximum number of results this API key can retrieve in one query. By default, there\'s no limit. */ maxHitsPerQuery?: number; /** - * Maximum number of API calls per hour allowed from a given IP address or [user token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken/). Each time an API call is performed with this key, a check is performed. If there were more than the specified number of calls within the last hour, the API returns an error with the status code `429` (Too Many Requests). > **Note**: Use this parameter to protect you from third-party attempts to retrieve your entire content by massively querying the index. + * Maximum number of API requests allowed per IP address or [user token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken/) per hour. If this limit is reached, the API returns an error with status code `429`. By default, there\'s no limit. */ maxQueriesPerIPPerHour?: number; /** - * Force some [query parameters](https://www.algolia.com/doc/api-reference/api-parameters/) to be applied for each query made with this API key. It\'s a URL-encoded query string. + * Query parameters to add when making API requests with this API key. To restrict this API key to specific IP addresses, add the `restrictSources` parameter. You can only add a single source, but you can provide a range of IP addresses. Creating an API key fails if the request is made from an IP address that\'s outside the restricted range. */ queryParameters?: string; /** - * Restrict this API key to specific [referrers](https://www.algolia.com/doc/guides/security/api-keys/in-depth/api-key-restrictions/#http-referrers). If empty, all referrers are allowed. For example: - `https://algolia.com/_*` matches all referrers starting with \"https://algolia.com/\" - `*.algolia.com` matches all referrers ending with \".algolia.com\" - `*algolia.com*` allows everything in the domain \"algolia.com\". + * Allowed HTTP referrers for this API key. By default, all referrers are allowed. You can use leading and trailing wildcard characters (`*`): - `https://algolia.com/_*` allows all referrers starting with \"https://algolia.com/\" - `*.algolia.com` allows all referrers ending with \".algolia.com\" - `*algolia.com*` allows all referrers in the domain \"algolia.com\". Like all HTTP headers, referrers can be spoofed. Don\'t rely on them to secure your data. For more information, see [HTTP referrer restrictions](https://www.algolia.com/doc/guides/security/security-best-practices/#http-referrers-restrictions). */ referers?: string[]; /** - * Validity duration of a key (in seconds). The key will automatically be removed after this time has expired. The default value of 0 never expires. Short-lived API keys are useful to grant temporary access to your data. For example, in mobile apps, you can\'t [control when users update your app](https://www.algolia.com/doc/guides/security/security-best-practices/#use-secured-api-keys-in-mobile-apps). So instead of encoding keys into your app as you would for a web app, you should dynamically fetch them from your mobile app\'s backend. + * Duration (in seconds) after which the API key expires. By default, API keys don\'t expire. */ validity?: number; }; diff --git a/packages/algoliasearch/lite/model/aroundPrecision.ts b/packages/algoliasearch/lite/model/aroundPrecision.ts index 71120c73e..937a1e87e 100644 --- a/packages/algoliasearch/lite/model/aroundPrecision.ts +++ b/packages/algoliasearch/lite/model/aroundPrecision.ts @@ -3,6 +3,6 @@ import type { AroundPrecisionFromValueInner } from './aroundPrecisionFromValueInner'; /** - * Precision of a geographical search (in meters), to [group results that are more or less the same distance from a central point](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/in-depth/geo-ranking-precision/). + * Precision of a coordinate-based search in meters to group results with similar distances. The Geo ranking criterion considers all matches within the same range of distances to be equal. */ export type AroundPrecision = AroundPrecisionFromValueInner[] | number; diff --git a/packages/algoliasearch/lite/model/aroundPrecisionFromValueInner.ts b/packages/algoliasearch/lite/model/aroundPrecisionFromValueInner.ts index 14a0e3bb7..c3850a800 100644 --- a/packages/algoliasearch/lite/model/aroundPrecisionFromValueInner.ts +++ b/packages/algoliasearch/lite/model/aroundPrecisionFromValueInner.ts @@ -1,7 +1,16 @@ // 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. +/** + * Range object with lower and upper values in meters to define custom ranges. + */ export type AroundPrecisionFromValueInner = { + /** + * Lower boundary of a range in meters. The Geo ranking criterion considers all records within the range to be equal. + */ from?: number; + /** + * Upper boundary of a range in meters. The Geo ranking criterion considers all records within the range to be equal. + */ value?: number; }; diff --git a/packages/algoliasearch/lite/model/aroundRadius.ts b/packages/algoliasearch/lite/model/aroundRadius.ts index 6c99817b2..1c4ae8df2 100644 --- a/packages/algoliasearch/lite/model/aroundRadius.ts +++ b/packages/algoliasearch/lite/model/aroundRadius.ts @@ -3,6 +3,6 @@ import type { AroundRadiusAll } from './aroundRadiusAll'; /** - * [Maximum radius](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#increase-the-search-radius) for a geographical search (in meters). + * Maximum radius for a search around a central location. This parameter works in combination with the `aroundLatLng` and `aroundLatLngViaIP` parameters. By default, the search radius is determined automatically from the density of hits around the central location. The search radius is small if there are many hits close to the central coordinates. */ export type AroundRadius = AroundRadiusAll | number; diff --git a/packages/algoliasearch/lite/model/aroundRadiusAll.ts b/packages/algoliasearch/lite/model/aroundRadiusAll.ts index 1dd22ed57..e5f107060 100644 --- a/packages/algoliasearch/lite/model/aroundRadiusAll.ts +++ b/packages/algoliasearch/lite/model/aroundRadiusAll.ts @@ -1,3 +1,6 @@ // 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. +/** + * Return all records with a valid `_geoloc` attribute. Don\'t filter by distance. + */ export type AroundRadiusAll = 'all'; diff --git a/packages/algoliasearch/lite/model/automaticFacetFilter.ts b/packages/algoliasearch/lite/model/automaticFacetFilter.ts index 98a2e1e7a..ca83695bf 100644 --- a/packages/algoliasearch/lite/model/automaticFacetFilter.ts +++ b/packages/algoliasearch/lite/model/automaticFacetFilter.ts @@ -1,21 +1,21 @@ // 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. /** - * Automatic facet Filter. + * Filter or optional filter to be applied to the search. */ export type AutomaticFacetFilter = { /** - * Attribute to filter on. This must match a facet placeholder in the Rule\'s pattern. + * Facet name to be applied as filter. The name must match placeholders in the `pattern` parameter. For example, with `pattern: {facet:genre}`, `automaticFacetFilters` must be `genre`. */ facet: string; /** - * Score for the filter. Typically used for optional or disjunctive filters. + * Filter scores to give different weights to individual filters. */ score?: number; /** - * Whether the filter is disjunctive (true) or conjunctive (false). + * Whether the filter is disjunctive or conjunctive. If true the filter has multiple matches, multiple occurences are combined with the logical `OR` operation. If false, multiple occurences are combined with the logical `AND` operation. */ disjunctive?: boolean; }; diff --git a/packages/algoliasearch/lite/model/automaticFacetFilters.ts b/packages/algoliasearch/lite/model/automaticFacetFilters.ts index 0ac46a30f..725561f8d 100644 --- a/packages/algoliasearch/lite/model/automaticFacetFilters.ts +++ b/packages/algoliasearch/lite/model/automaticFacetFilters.ts @@ -3,6 +3,6 @@ import type { AutomaticFacetFilter } from './automaticFacetFilter'; /** - * Names of facets to which automatic filtering must be applied; they must match the facet name of a facet value placeholder in the query pattern. + * Filter to be applied to the search. You can use this to respond to search queries that match a facet value. For example, if users search for \"comedy\", which matches a facet value of the \"genre\" facet, you can filter the results to show the top-ranked comedy movies. */ export type AutomaticFacetFilters = AutomaticFacetFilter[] | string[]; diff --git a/packages/algoliasearch/lite/model/baseIndexSettings.ts b/packages/algoliasearch/lite/model/baseIndexSettings.ts index 3d026541d..a35d8cbd3 100644 --- a/packages/algoliasearch/lite/model/baseIndexSettings.ts +++ b/packages/algoliasearch/lite/model/baseIndexSettings.ts @@ -2,82 +2,87 @@ export type BaseIndexSettings = { /** - * Creates [replicas](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/replicas/), which are copies of a primary index with the same records but different settings. + * Attributes used for [faceting](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/). Facets are ways to categorize search results based on attributes. Facets can be used to let user filter search results. By default, no attribute is used for faceting. **Modifiers**
filterOnly(\"ATTRIBUTE\")
Allows using this attribute as a filter, but doesn\'t evalue the facet values.
searchable(\"ATTRIBUTE\")
Allows searching for facet values.
afterDistinct(\"ATTRIBUTE\")
Evaluates the facet count _after_ deduplication with `distinct`. This ensures accurate facet counts. You can apply this modifier to searchable facets: `afterDistinct(searchable(ATTRIBUTE))`.
Without modifiers, the attribute is used as a regular facet. + */ + attributesForFaceting?: string[]; + + /** + * Creates [replica indices](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/replicas/). Replicas are copies of a primary index with the same records but different settings, synonyms, or rules. If you want to offer a different ranking or sorting of your search results, you\'ll use replica indices. All index operations on a primary index are automatically forwarded to its replicas. To add a replica index, you must provide the complete set of replicas to this parameter. If you omit a replica from this list, the replica turns into a regular, standalone index that will no longer by synced with the primary index. **Modifier**
virtual(\"REPLICA\")
Create a virtual replica, Virtual replicas don\'t increase the number of records and are optimized for [Relevant sorting](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/relevant-sort/).
Without modifier, a standard replica is created, which duplicates your record count and is used for strict, or [exhaustive sorting](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/exhaustive-sort/). */ replicas?: string[]; /** - * Maximum number of hits accessible through pagination. + * Maximum number of search results that can be obtained through pagination. Higher pagination limits might slow down your search. For pagination limits above 1,000, the sorting of results beyond the 1,000th hit can\'t be guaranteed. */ paginationLimitedTo?: number; /** - * Attributes that can\'t be retrieved at query time. + * Attributes that can\'t be retrieved at query time. This can be useful if you want to use an attribute for ranking or to [restrict access](https://www.algolia.com/doc/guides/security/api-keys/how-to/user-restricted-access-to-data/), but don\'t want to include it in the search results. */ unretrievableAttributes?: string[]; /** - * Words for which you want to turn off [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/). + * 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. */ disableTypoToleranceOnWords?: string[]; /** - * Attributes in your index to which [Japanese transliteration](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/#japanese-transliteration-and-type-ahead) applies. This will ensure that words indexed in Katakana or Kanji can also be searched in Hiragana. + * Attributes, for which you want to support [Japanese transliteration](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/#japanese-transliteration-and-type-ahead). Transliteration supports searching in any of the Japanese writing systems. To support transliteration, you must set the indexing language to Japanese. */ attributesToTransliterate?: string[]; /** - * Attributes on which to split [camel case](https://wikipedia.org/wiki/Camel_case) words. + * Attributes for which to split [camel case](https://wikipedia.org/wiki/Camel_case) words. */ camelCaseAttributes?: string[]; /** - * Attributes in your index to which [word segmentation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/how-to/customize-segmentation/) (decompounding) applies. + * Searchable attributes to which Algolia should apply [word segmentation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/how-to/customize-segmentation/) (decompounding). Compound words are formed by combining two or more individual words, and are particularly prevalent in Germanic languages—for example, \"firefighter\". With decompounding, the individual components are indexed separately. You can specify different lists for different languages. Decompounding is supported for these languages: Dutch (`nl`), German (`de`), Finnish (`fi`), Danish (`da`), Swedish (`sv`), and Norwegian (`no`). */ decompoundedAttributes?: Record; /** - * Set the languages of your index, for language-specific processing steps such as [tokenization](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/tokenization/) and [normalization](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/normalization/). + * [ISO code](https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes) for a language for language-specific processing steps, such as word detection and dictionary settings. **You should always specify an indexing 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/). */ indexLanguages?: string[]; /** - * Attributes for which you want to turn off [prefix matching](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/#adjusting-prefix-search). + * Searchable attributes for which you want to turn off [prefix matching](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/#adjusting-prefix-search). */ disablePrefixOnAttributes?: string[]; /** - * Incidates whether the engine compresses arrays with exclusively non-negative integers. When enabled, the compressed arrays may be reordered. + * Whether arrays with exclusively non-negative integers should be compressed for better performance. If true, the compressed arrays may be reordered. */ allowCompressionOfIntegerArray?: boolean; /** - * Numeric attributes that can be used as [numerical filters](https://www.algolia.com/doc/guides/managing-results/rules/detecting-intent/how-to/applying-a-custom-filter-for-a-specific-query/#numerical-filters). + * Numeric attributes that can be used as [numerical filters](https://www.algolia.com/doc/guides/managing-results/rules/detecting-intent/how-to/applying-a-custom-filter-for-a-specific-query/#numerical-filters). By default, all numeric attributes are available as numerical filters. For faster indexing, reduce the number of numeric attributes. If you want to turn off filtering for all numeric attributes, specifiy an attribute that doesn\'t exist in your index, such as `NO_NUMERIC_FILTERING`. **Modifier**
equalOnly(\"ATTRIBUTE\")
Support only filtering based on equality comparisons `=` and `!=`.
Without modifier, all numeric comparisons are supported. */ numericAttributesForFiltering?: string[]; /** - * Controls which separators are added to an Algolia index as part of [normalization](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/#what-does-normalization-mean). Separators are all non-letter characters except spaces and currency characters, such as $€£¥. + * 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. */ separatorsToIndex?: string; /** - * [Attributes used for searching](https://www.algolia.com/doc/guides/managing-results/must-do/searchable-attributes/), including determining [if matches at the beginning of a word are important (ordered) or not (unordered)](https://www.algolia.com/doc/guides/managing-results/must-do/searchable-attributes/how-to/configuring-searchable-attributes-the-right-way/#understanding-word-position). + * Attributes used for searching. By default, all attributes are searchable and the [Attribute](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#attribute) ranking criterion is turned off. With a non-empty list, Algolia only returns results with matches in the selected attributes. In addition, the Attribute ranking criterion is turned on: matches in attributes that are higher in the list of `searchableAttributes` rank first. To make matches in two attributes rank equally, include them in a comma-separated string, such as `\"title,alternate_title\"`. Attributes with the same priority are always unordered. For more information, see [Searchable attributes](https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/how-to/setting-searchable-attributes/). **Modifier**
unordered(\"ATTRIBUTE\")
Ignore the position of a match within the attribute.
Without modifier, matches at the beginning of an attribute rank higer than matches at the end. */ searchableAttributes?: string[]; /** - * Lets you store custom data in your indices. + * An object with custom data. You can store up to 32 kB as custom data. */ userData?: any | null; /** - * A list of characters and their normalized replacements to override Algolia\'s default [normalization](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/normalization/). + * Characters and their normalized replacements. This overrides Algolia\'s default [normalization](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/normalization/). */ customNormalization?: Record>; /** - * Name of the deduplication attribute to be used with Algolia\'s [_distinct_ feature](https://www.algolia.com/doc/guides/managing-results/refine-results/grouping/#introducing-algolias-distinct-feature). + * Attribute that should be used to establish groups of results. All records with the same value for this attribute are considered a group. You can combine `attributeForDistinct` with the `distinct` search parameter to control how many items per group are included in the search results. If you want to use the same attribute also for faceting, use the `afterDistinct` modifier of the `attributesForFaceting` setting. This applies faceting _after_ deduplication, which will result in accurate facet counts. */ attributeForDistinct?: string; }; diff --git a/packages/algoliasearch/lite/model/baseSearchParamsWithoutQuery.ts b/packages/algoliasearch/lite/model/baseSearchParamsWithoutQuery.ts index 33825f13f..95ae5b039 100644 --- a/packages/algoliasearch/lite/model/baseSearchParamsWithoutQuery.ts +++ b/packages/algoliasearch/lite/model/baseSearchParamsWithoutQuery.ts @@ -9,12 +9,12 @@ import type { TagFilters } from './tagFilters'; export type BaseSearchParamsWithoutQuery = { /** - * Overrides the query parameter and performs a more generic search. + * 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](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering/) the query with numeric, facet, or tag filters. + * Filter the search so that only records with matching values are included in the results. These filters are supported: - **Numeric filters.** ` `, where `` is one of `<`, `<=`, `=`, `!=`, `>`, `>=`. - **Ranges.** `: TO ` where `` and `` are the lower and upper limits of the range (inclusive). - **Facet filters.** `:` where `` is a facet attribute (case-sensitive) and `` a facet value. - **Tag filters.** `_tags:` or just `` (case-sensitive). - **Boolean filters.** `: 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; @@ -27,47 +27,47 @@ export type BaseSearchParamsWithoutQuery = { tagFilters?: TagFilters; /** - * Determines how to calculate [filter scores](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering/in-depth/filter-scoring/#accumulating-scores-with-sumorfiltersscores). If `false`, maximum score is kept. If `true`, score is summed. + * 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 query to only look at a subset of your [searchable attributes](https://www.algolia.com/doc/guides/managing-results/must-do/searchable-attributes/). + * Restricts a search to a subset of your searchable attributes. */ restrictSearchableAttributes?: string[]; /** - * Returns [facets](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#contextual-facet-values-and-counts), their facet values, and the number of matching facet values. + * 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?: string[]; /** - * Forces faceting to be applied after [de-duplication](https://www.algolia.com/doc/guides/managing-results/refine-results/grouping/) (with the distinct feature). Alternatively, the `afterDistinct` [modifier](https://www.algolia.com/doc/api-reference/api-parameters/attributesForFaceting/#modifiers) of `attributesForFaceting` allows for more granular control. + * 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; /** - * Page to retrieve (the first page is `0`, not `1`). + * Page of search results to retrieve. */ page?: number; /** - * Specifies the offset of the first hit to return. > **Note**: Using `page` and `hitsPerPage` is the recommended method for [paging results](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/). However, you can use `offset` and `length` to implement [an alternative approach to paging](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/#retrieving-a-subset-of-records-with-offset-and-length). + * Position of the first hit to retrieve. */ offset?: number; /** - * Sets the number of hits to retrieve (for use with `offset`). > **Note**: Using `page` and `hitsPerPage` is the recommended method for [paging results](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/). However, you can use `offset` and `length` to implement [an alternative approach to paging](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/#retrieving-a-subset-of-records-with-offset-and-length). + * Number of hits to retrieve (used in combination with `offset`). */ length?: number; /** - * Search for entries [around a central location](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filter-around-a-central-point), enabling a geographical search within a circular area. + * Coordinates for the center of a circle, expressed as a comma-separated string of latitude and longitude. Only records included within 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; /** - * Search for entries around a location. The location is automatically computed from the requester\'s IP address. + * Whether to obtain the coordinates from the request\'s IP address. */ aroundLatLngViaIP?: boolean; @@ -76,62 +76,57 @@ export type BaseSearchParamsWithoutQuery = { aroundPrecision?: AroundPrecision; /** - * Minimum radius (in meters) used for a geographical search when `aroundRadius` isn\'t set. + * Minimum radius (in meters) for a search around a location when `aroundRadius` isn\'t set. */ minimumAroundRadius?: number; /** - * Search inside a [rectangular area](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas) (in geographical coordinates). + * 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?: number[][]; /** - * Search inside a [polygon](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas) (in geographical coordinates). + * 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?: number[][]; /** - * Changes the default values of parameters that work best for a natural language query, such as `ignorePlurals`, `removeStopWords`, `removeWordsIfNoResults`, `analyticsTags`, and `ruleContexts`. These parameters work well together when the query consists of fuller natural language strings instead of keywords, for example when processing voice search queries. + * 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?: string[]; /** - * Assigns [rule contexts](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/how-to/customize-search-results-by-platform/#whats-a-context) to search queries. + * 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?: string[]; /** - * Defines how much [Personalization affects results](https://www.algolia.com/doc/guides/personalization/personalizing-results/in-depth/configuring-personalization/#understanding-personalization-impact). + * 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; /** - * Associates a [user token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken/) with the current search. + * 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; /** - * Incidates whether the search response includes [detailed ranking information](https://www.algolia.com/doc/guides/building-search-ui/going-further/backend-search/in-depth/understanding-the-api-response/#ranking-information). + * Whether the search response should include detailed ranking information. */ getRankingInfo?: boolean; /** - * Enriches the API\'s response with information about how the query was processed. - */ - explain?: string[]; - - /** - * Whether to take into account an index\'s synonyms for a particular search. + * Whether to take into account an index\'s synonyms for this search. */ synonyms?: boolean; /** - * Indicates whether a query ID parameter is included in the search response. This is required for [tracking click and conversion events](https://www.algolia.com/doc/guides/sending-events/concepts/event-types/#events-related-to-algolia-requests). + * 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; /** - * Indicates whether this query will be included in [analytics](https://www.algolia.com/doc/guides/search-analytics/guides/exclude-queries/). + * Whether this search will be included in Analytics. */ analytics?: boolean; @@ -141,12 +136,12 @@ export type BaseSearchParamsWithoutQuery = { analyticsTags?: string[]; /** - * Whether to include or exclude a query from the processing-time percentile computation. + * Whether to include this search when calculating processing-time percentiles. */ percentileComputation?: boolean; /** - * Incidates whether this search will be considered in A/B testing. + * Whether to enable A/B testing for this search. */ enableABTest?: boolean; }; diff --git a/packages/algoliasearch/lite/model/baseSearchResponse.ts b/packages/algoliasearch/lite/model/baseSearchResponse.ts index abd29c39d..6d3dd06f9 100644 --- a/packages/algoliasearch/lite/model/baseSearchResponse.ts +++ b/packages/algoliasearch/lite/model/baseSearchResponse.ts @@ -22,7 +22,7 @@ export type BaseSearchResponse = Record & { aroundLatLng?: string; /** - * Automatically-computed radius. + * Distance from a central coordinate provided by `aroundLatLng`. */ automaticRadius?: string; @@ -44,7 +44,7 @@ export type BaseSearchResponse = Record & { exhaustiveTypo?: boolean; /** - * Mapping of each facet name to the corresponding facet counts. + * Facet counts. */ facets?: Record>; @@ -74,12 +74,12 @@ export type BaseSearchResponse = Record & { message?: string; /** - * Number of hits the search query matched. + * Number of results (hits). */ nbHits: number; /** - * Number of pages of results for the current query. + * Number of pages of results. */ nbPages: number; @@ -89,7 +89,7 @@ export type BaseSearchResponse = Record & { nbSortedHits?: number; /** - * Page to retrieve (the first page is `0`, not `1`). + * Page of search results to retrieve. */ page: number; @@ -128,7 +128,7 @@ export type BaseSearchResponse = Record & { serverUsed?: string; /** - * Lets you store custom data in your indices. + * An object with custom data. You can store up to 32 kB as custom data. */ userData?: any | null; diff --git a/packages/algoliasearch/lite/model/builtInOperation.ts b/packages/algoliasearch/lite/model/builtInOperation.ts index 8bcf7b094..d3df17410 100644 --- a/packages/algoliasearch/lite/model/builtInOperation.ts +++ b/packages/algoliasearch/lite/model/builtInOperation.ts @@ -3,13 +3,13 @@ import type { BuiltInOperationType } from './builtInOperationType'; /** - * To update an attribute without pushing the entire record, you can use these built-in operations. + * Update to perform on the attribute. */ export type BuiltInOperation = { _operation: BuiltInOperationType; /** - * Value that corresponds to the operation, for example an `Increment` or `Decrement` step, `Add` or `Remove` value. + * Value that corresponds to the operation, for example an `Increment` or `Decrement` step, or an `Add` or `Remove` value. */ value: string; }; diff --git a/packages/algoliasearch/lite/model/builtInOperationType.ts b/packages/algoliasearch/lite/model/builtInOperationType.ts index 71a7cd154..56d0ed532 100644 --- a/packages/algoliasearch/lite/model/builtInOperationType.ts +++ b/packages/algoliasearch/lite/model/builtInOperationType.ts @@ -1,7 +1,7 @@ // 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. /** - * Operation to apply to the attribute. + * How to change the attribute. */ export type BuiltInOperationType = | 'Add' diff --git a/packages/algoliasearch/lite/model/condition.ts b/packages/algoliasearch/lite/model/condition.ts index bb600e8c4..fea1e6776 100644 --- a/packages/algoliasearch/lite/model/condition.ts +++ b/packages/algoliasearch/lite/model/condition.ts @@ -4,19 +4,24 @@ import type { Anchoring } from './anchoring'; export type Condition = { /** - * Query pattern syntax. + * Query pattern that triggers the rule. You can use either a literal string, or a special pattern `{facet:ATTRIBUTE}`, where `ATTRIBUTE` is a facet name. The rule is triggered if the query matches the literal string or a value of the specified facet. For example, with `pattern: {facet:genre}`, the rule is triggered when users search for a genre, such as \"comedy\". */ pattern?: string; anchoring?: Anchoring; /** - * Whether the pattern matches on plurals, synonyms, and typos. + * Whether the pattern should match plurals, synonyms, and typos. */ alternatives?: boolean; /** - * Rule context format: [A-Za-z0-9_-]+). + * An additional restriction that only triggers the rule, when the search has the same value as `ruleContexts` parameter. For example, if `context: mobile`, the rule is only triggered when the search request has a matching `ruleContexts: mobile`. A rule context must only contain alphanumeric characters. */ context?: string; + + /** + * Filters that trigger the rule. You can add add filters using the syntax `facet:value` so that the rule is triggered, when the specific filter is selected. You can use `filters` on its own or combine it with the `pattern` parameter. + */ + filters?: string; }; diff --git a/packages/algoliasearch/lite/model/consequence.ts b/packages/algoliasearch/lite/model/consequence.ts index be9aa688d..a24c7e3a8 100644 --- a/packages/algoliasearch/lite/model/consequence.ts +++ b/packages/algoliasearch/lite/model/consequence.ts @@ -5,28 +5,28 @@ import type { ConsequenceParams } from './consequenceParams'; import type { Promote } from './promote'; /** - * [Consequences](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/#consequences) of a rule. + * Effect of the rule. For more information, see [Consequences](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/#consequences). */ export type Consequence = { params?: ConsequenceParams; /** - * Records to promote. + * Records you want to pin to a specific position in the search results. You can promote up to 300 records, either individually, or as groups of up to 100 records each. */ promote?: Promote[]; /** - * Only use in combination with the `promote` consequence. When `true`, promoted results will be restricted to match the filters of the current search. When `false`, the promoted results will show up regardless of the filters. + * Whether promoted records must match an active filter for the consequence to be applied. This ensures that user actions (filtering the search) are given a higher precendence. For example, if you promote a record with the `color: red` attribute, and the user filters the search for `color: blue`, the \"red\" record won\'t be shown. */ filterPromotes?: boolean; /** - * Records to hide. By default, you can hide up to 50 records per rule. + * Records you want to hide from the search results. */ hide?: ConsequenceHide[]; /** - * Custom JSON object that will be appended to the userData array in the response. This object isn\'t interpreted by the API. It\'s limited to 1kB of minified JSON. + * A JSON object with custom data that will be appended to the `userData` array in the response. This object isn\'t interpreted by the API and is limited to 1 kB of minified JSON. */ userData?: any | null; }; diff --git a/packages/algoliasearch/lite/model/consequenceHide.ts b/packages/algoliasearch/lite/model/consequenceHide.ts index ff8731ed7..9ef5cf251 100644 --- a/packages/algoliasearch/lite/model/consequenceHide.ts +++ b/packages/algoliasearch/lite/model/consequenceHide.ts @@ -1,11 +1,11 @@ // 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. /** - * Unique identifier of the record to hide. + * Object ID of the record to hide. */ export type ConsequenceHide = { /** - * Unique object identifier. + * Unique record identifier. */ objectID: string; }; diff --git a/packages/algoliasearch/lite/model/consequenceQuery.ts b/packages/algoliasearch/lite/model/consequenceQuery.ts index 464cb5325..28d8722a3 100644 --- a/packages/algoliasearch/lite/model/consequenceQuery.ts +++ b/packages/algoliasearch/lite/model/consequenceQuery.ts @@ -3,6 +3,6 @@ import type { ConsequenceQueryObject } from './consequenceQueryObject'; /** - * When providing a string, it replaces the entire query string. When providing an object, it describes incremental edits to be made to the query string (but you can\'t do both). + * Replace or edit the search query. If `consequenceQuery` is a string, the entire search query is replaced with that string. If `consequenceQuery` is an object, it describes incremental edits made to the query. */ export type ConsequenceQuery = ConsequenceQueryObject | string; diff --git a/packages/algoliasearch/lite/model/consequenceQueryObject.ts b/packages/algoliasearch/lite/model/consequenceQueryObject.ts index 4aedb781e..6d12dbc8a 100644 --- a/packages/algoliasearch/lite/model/consequenceQueryObject.ts +++ b/packages/algoliasearch/lite/model/consequenceQueryObject.ts @@ -4,12 +4,12 @@ import type { Edit } from './edit'; export type ConsequenceQueryObject = { /** - * Words to remove. + * Words to remove from the search query. */ remove?: string[]; /** - * Edits to apply. + * Changes to make to the search query. */ edits?: Edit[]; }; diff --git a/packages/algoliasearch/lite/model/cursor.ts b/packages/algoliasearch/lite/model/cursor.ts index b645bb3aa..db36a6129 100644 --- a/packages/algoliasearch/lite/model/cursor.ts +++ b/packages/algoliasearch/lite/model/cursor.ts @@ -2,7 +2,7 @@ export type Cursor = { /** - * Cursor indicating the location to resume browsing from. Must match the value returned by the previous call. Pass this value to the subsequent browse call to get the next page of results. When the end of the index has been reached, `cursor` is absent from the response. + * Cursor to get the next page of the response. The parameter must match the value returned in the response of a previous request. The last page of the response does not return a `cursor` attribute. */ cursor?: string; }; diff --git a/packages/algoliasearch/lite/model/deleteByParams.ts b/packages/algoliasearch/lite/model/deleteByParams.ts index 776c9c8d3..ff6681d83 100644 --- a/packages/algoliasearch/lite/model/deleteByParams.ts +++ b/packages/algoliasearch/lite/model/deleteByParams.ts @@ -9,7 +9,7 @@ export type DeleteByParams = { facetFilters?: FacetFilters; /** - * [Filter](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering/) the query with numeric, facet, or tag filters. + * Filter the search so that only records with matching values are included in the results. These filters are supported: - **Numeric filters.** ` `, where `` is one of `<`, `<=`, `=`, `!=`, `>`, `>=`. - **Ranges.** `: TO ` where `` and `` are the lower and upper limits of the range (inclusive). - **Facet filters.** `:` where `` is a facet attribute (case-sensitive) and `` a facet value. - **Tag filters.** `_tags:` or just `` (case-sensitive). - **Boolean filters.** `: 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; @@ -18,19 +18,19 @@ export type DeleteByParams = { tagFilters?: TagFilters; /** - * Search for entries [around a central location](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filter-around-a-central-point), enabling a geographical search within a circular area. + * Coordinates for the center of a circle, expressed as a comma-separated string of latitude and longitude. Only records included within 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; aroundRadius?: AroundRadius; /** - * Search inside a [rectangular area](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas) (in geographical coordinates). + * 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?: number[][]; /** - * Search inside a [polygon](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas) (in geographical coordinates). + * 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?: number[][]; }; diff --git a/packages/algoliasearch/lite/model/dictionaryEntry.ts b/packages/algoliasearch/lite/model/dictionaryEntry.ts index 807f90270..2a832ca4b 100644 --- a/packages/algoliasearch/lite/model/dictionaryEntry.ts +++ b/packages/algoliasearch/lite/model/dictionaryEntry.ts @@ -7,27 +7,27 @@ import type { DictionaryEntryState } from './dictionaryEntryState'; */ export type DictionaryEntry = Record & { /** - * Unique identifier for a dictionary object. + * Unique identifier for the dictionary entry. */ objectID: string; /** - * [Supported language ISO code](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages/). + * ISO code of a [supported language](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages/). */ language: string; /** - * Dictionary entry word. Usage depends on the type of dictionary entry. **`stopwordEntry`** The stop word you want to add or update. If the entry already exists in Algolia\'s standard dictionary, you can override its behavior by adding it to the custom dictionary and setting its `state` to `disabled`. **`compoundEntry`** When `decomposition` is empty: adds `word` as a compound atom. For example, atom “kino” decomposes the query “kopfkino” into \"kopf\" and \"kino\". When `decomposition` isn\'t empty: creates a decomposition exception. For example, when decomposition is set to the [\"hund\", \"hutte\"] exception, \"hundehutte\" decomposes into “hund” and “hutte”, discarding the linking \"e\". + * Matching dictionary word for `stopwords` and `compounds` dictionaries. */ word?: string; /** - * Compound dictionary [word declensions](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/how-to/customize-plurals-and-other-declensions/). If the entry already exists in Algolia\'s standard dictionary, you can override its behavior by adding it to the custom dictionary and setting its `state` to `disabled`. + * Matching words in the `plurals` dictionary including declensions. */ words?: string[]; /** - * For compound entries, governs the behavior of the `word` parameter. + * Invividual components of a compound word in the `compounds` dictionary. */ decomposition?: string[]; diff --git a/packages/algoliasearch/lite/model/dictionaryEntryState.ts b/packages/algoliasearch/lite/model/dictionaryEntryState.ts index 785180236..5ea78345d 100644 --- a/packages/algoliasearch/lite/model/dictionaryEntryState.ts +++ b/packages/algoliasearch/lite/model/dictionaryEntryState.ts @@ -1,6 +1,6 @@ // 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. /** - * Indicates whether a dictionary entry is active (`enabled`) or inactive (`disabled`). + * Whether a dictionary entry is active. */ export type DictionaryEntryState = 'disabled' | 'enabled'; diff --git a/packages/algoliasearch/lite/model/dictionaryLanguage.ts b/packages/algoliasearch/lite/model/dictionaryLanguage.ts index 4335e2cfe..7858762a1 100644 --- a/packages/algoliasearch/lite/model/dictionaryLanguage.ts +++ b/packages/algoliasearch/lite/model/dictionaryLanguage.ts @@ -1,11 +1,11 @@ // 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. /** - * Custom entries for a dictionary. + * Dictionary type. If `null`, this dictionary type isn\'t supported for the language. */ export type DictionaryLanguage = { /** - * If `0`, the dictionary hasn\'t been customized and only contains standard entries provided by Algolia. If `null`, that feature isn\'t available or isn\'t supported for that language. + * Number of custom dictionary entries. */ nbCustomEntries?: number; }; diff --git a/packages/algoliasearch/lite/model/distinct.ts b/packages/algoliasearch/lite/model/distinct.ts index 1779d9741..dc87dfb00 100644 --- a/packages/algoliasearch/lite/model/distinct.ts +++ b/packages/algoliasearch/lite/model/distinct.ts @@ -1,6 +1,6 @@ // 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. /** - * Enables [deduplication or grouping of results (Algolia\'s _distinct_ feature](https://www.algolia.com/doc/guides/managing-results/refine-results/grouping/#introducing-algolias-distinct-feature)). + * Determines how many records of a group are included in the search results. Records with the same value for the `attributeForDistinct` attribute are considered a group. The `distinct` setting controls how many members of the group are returned. This is useful for [deduplication and grouping](https://www.algolia.com/doc/guides/managing-results/refine-results/grouping/#introducing-algolias-distinct-feature). The `distinct` setting is ignored if `attributeForDistinct` is not set. */ export type Distinct = boolean | number; diff --git a/packages/algoliasearch/lite/model/edit.ts b/packages/algoliasearch/lite/model/edit.ts index 9c11afef4..b77d006e3 100644 --- a/packages/algoliasearch/lite/model/edit.ts +++ b/packages/algoliasearch/lite/model/edit.ts @@ -11,7 +11,7 @@ export type Edit = { delete?: string; /** - * Text that should be inserted in place of the removed text inside the query string. + * Text to be added in place of the deleted text inside the query string. */ insert?: string; }; diff --git a/packages/algoliasearch/lite/model/exactOnSingleWordQuery.ts b/packages/algoliasearch/lite/model/exactOnSingleWordQuery.ts index 6d5747887..bad4a2bae 100644 --- a/packages/algoliasearch/lite/model/exactOnSingleWordQuery.ts +++ b/packages/algoliasearch/lite/model/exactOnSingleWordQuery.ts @@ -1,6 +1,6 @@ // 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. /** - * Determines how 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) is computed when the query contains only one word. + * Determines how 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) is computed when the search query has only one word.
attribute
The Exact ranking criterion is 1 if the query word and attribute value are the same. For example, a search for \"road\" will match the value \"road\", but not \"road trip\".
none
The Exact ranking criterion is ignored on single-word searches.
word
The Exact ranking criterion is 1 if the query word is found in the attribute value. The query word must have at least 3 characters and must not be a stop word.
If `exactOnSingleWordQuery` is `word`, only exact matches will be highlighted, partial and prefix matches won\'t. */ export type ExactOnSingleWordQuery = 'attribute' | 'none' | 'word'; diff --git a/packages/algoliasearch/lite/model/facetFilters.ts b/packages/algoliasearch/lite/model/facetFilters.ts index e9eae1db3..f83f2eea3 100644 --- a/packages/algoliasearch/lite/model/facetFilters.ts +++ b/packages/algoliasearch/lite/model/facetFilters.ts @@ -3,6 +3,6 @@ import type { MixedSearchFilters } from './mixedSearchFilters'; /** - * [Filter hits by facet value](https://www.algolia.com/doc/api-reference/api-parameters/facetFilters/). + * Filter the search by facet values, so that only records with the same facet values are retrieved. **Prefer using the `filters` parameter, which supports all filter types and combinations with boolean operators.** - `[filter1, filter2]` is interpreted as `filter1 AND filter2`. - `[[filter1, filter2], filter3]` is interpreted as `filter1 OR filter2 AND filter3`. - `facet:-value` is interpreted as `NOT facet:value`. While it\'s best to avoid attributes that start with a `-`, you can still filter them by escaping with a backslash: `facet:\\-value`. */ export type FacetFilters = MixedSearchFilters[] | string; diff --git a/packages/algoliasearch/lite/model/facetHits.ts b/packages/algoliasearch/lite/model/facetHits.ts index 06d0ffb9c..bd205a61e 100644 --- a/packages/algoliasearch/lite/model/facetHits.ts +++ b/packages/algoliasearch/lite/model/facetHits.ts @@ -7,12 +7,12 @@ export type FacetHits = { value: string; /** - * Markup text with `facetQuery` matches highlighted. + * Highlighted attribute value, including HTML tags. */ highlighted: string; /** - * Number of records containing this facet value. This takes into account the extra search parameters specified in the query. Like for a regular search query, the [counts may not be exhaustive](https://support.algolia.com/hc/en-us/articles/4406975248145-Why-are-my-facet-and-hit-counts-not-accurate-). + * Number of records with this facet value. [The count may be approximated](https://support.algolia.com/hc/en-us/articles/4406975248145-Why-are-my-facet-and-hit-counts-not-accurate-). */ count: number; }; diff --git a/packages/algoliasearch/lite/model/facetOrdering.ts b/packages/algoliasearch/lite/model/facetOrdering.ts index 4e1af92fd..9e057ded5 100644 --- a/packages/algoliasearch/lite/model/facetOrdering.ts +++ b/packages/algoliasearch/lite/model/facetOrdering.ts @@ -4,13 +4,13 @@ import type { Facets } from './facets'; import type { Value } from './value'; /** - * Defines the ordering of facets (widgets). + * Order of facet names and facet values in your UI. */ export type FacetOrdering = { facets?: Facets; /** - * Ordering of facet values within an individual facet. + * Order of facet values. One object for each facet. */ values?: Record; }; diff --git a/packages/algoliasearch/lite/model/facets.ts b/packages/algoliasearch/lite/model/facets.ts index b10eb0f3c..3aefad3a5 100644 --- a/packages/algoliasearch/lite/model/facets.ts +++ b/packages/algoliasearch/lite/model/facets.ts @@ -1,11 +1,11 @@ // 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. /** - * Ordering of facets (widgets). + * Order of facet names. */ export type Facets = { /** - * Pinned order of facet lists. + * Explicit order of facets or facet values. This setting lets you always show specific facets or facet values at the top of the list. */ order?: string[]; }; diff --git a/packages/algoliasearch/lite/model/highlightResultOption.ts b/packages/algoliasearch/lite/model/highlightResultOption.ts index 7d68dce0e..0de083fe2 100644 --- a/packages/algoliasearch/lite/model/highlightResultOption.ts +++ b/packages/algoliasearch/lite/model/highlightResultOption.ts @@ -3,18 +3,18 @@ import type { MatchLevel } from './matchLevel'; /** - * Show highlighted section and words matched on a query. + * Surround words that match the query with HTML tags for highlighting. */ export type HighlightResultOption = { /** - * Markup text with `facetQuery` matches highlighted. + * Highlighted attribute value, including HTML tags. */ value: string; matchLevel: MatchLevel; /** - * List of words from the query that matched the object. + * List of matched words from the search query. */ matchedWords: string[]; diff --git a/packages/algoliasearch/lite/model/hit.ts b/packages/algoliasearch/lite/model/hit.ts index d670f4df4..9c0028146 100644 --- a/packages/algoliasearch/lite/model/hit.ts +++ b/packages/algoliasearch/lite/model/hit.ts @@ -5,21 +5,21 @@ import type { RankingInfo } from './rankingInfo'; import type { SnippetResult } from './snippetResult'; /** - * A single hit. + * Search result. A hit is a record from your index, augmented with special attributes for highlighting, snippeting, and ranking. */ export type Hit> = T & { /** - * Unique object identifier. + * Unique record identifier. */ objectID: string; /** - * Show highlighted section and words matched on a query. + * Surround words that match the query with HTML tags for highlighting. */ _highlightResult?: Record; /** - * Snippeted attributes show parts of the matched attributes. Only returned when attributesToSnippet is non-empty. + * Snippets that show the context around a matching search query. */ _snippetResult?: Record; diff --git a/packages/algoliasearch/lite/model/ignorePlurals.ts b/packages/algoliasearch/lite/model/ignorePlurals.ts index ffea12b13..e02272856 100644 --- a/packages/algoliasearch/lite/model/ignorePlurals.ts +++ b/packages/algoliasearch/lite/model/ignorePlurals.ts @@ -1,6 +1,6 @@ // 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. /** - * Treats singular, plurals, and other forms of declensions as matching terms. `ignorePlurals` is used in conjunction with the `queryLanguages` setting. _list_: language ISO codes for which ignoring plurals should be enabled. This list will override any values that you may have set in `queryLanguages`. _true_: enables the ignore plurals feature, where singulars and plurals are considered equivalent (\"foot\" = \"feet\"). The languages supported here are either [every language](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages/) (this is the default) or those set by `queryLanguages`. _false_: turns off the ignore plurals feature, so that singulars and plurals aren\'t considered to be the same (\"foot\" will not find \"feet\"). + * Treat singular, plurals, and other forms of declensions as equivalent. You should only use this feature for the languages used in your index. */ export type IgnorePlurals = string[] | boolean; diff --git a/packages/algoliasearch/lite/model/index.ts b/packages/algoliasearch/lite/model/index.ts index 3dcf44d60..5f6092a3b 100644 --- a/packages/algoliasearch/lite/model/index.ts +++ b/packages/algoliasearch/lite/model/index.ts @@ -83,6 +83,7 @@ export * from './removeWordsIfNoResults'; export * from './renderingContent'; export * from './rule'; export * from './scopeType'; +export * from './searchDictionaryEntriesResponse'; export * from './searchForFacetValuesResponse'; export * from './searchForFacets'; export * from './searchForFacetsOptions'; diff --git a/packages/algoliasearch/lite/model/indexSettings.ts b/packages/algoliasearch/lite/model/indexSettings.ts index 4ef41b83d..7f2e9acde 100644 --- a/packages/algoliasearch/lite/model/indexSettings.ts +++ b/packages/algoliasearch/lite/model/indexSettings.ts @@ -4,6 +4,6 @@ import type { BaseIndexSettings } from './baseIndexSettings'; import type { IndexSettingsAsSearchParams } from './indexSettingsAsSearchParams'; /** - * Algolia index settings. + * Index settings. */ export type IndexSettings = BaseIndexSettings & IndexSettingsAsSearchParams; diff --git a/packages/algoliasearch/lite/model/indexSettingsAsSearchParams.ts b/packages/algoliasearch/lite/model/indexSettingsAsSearchParams.ts index 765e380d1..b946517d8 100644 --- a/packages/algoliasearch/lite/model/indexSettingsAsSearchParams.ts +++ b/packages/algoliasearch/lite/model/indexSettingsAsSearchParams.ts @@ -16,47 +16,42 @@ import type { TypoTolerance } from './typoTolerance'; export type IndexSettingsAsSearchParams = { /** - * Attributes used for [faceting](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/) and the [modifiers](https://www.algolia.com/doc/api-reference/api-parameters/attributesForFaceting/#modifiers) that can be applied: `filterOnly`, `searchable`, and `afterDistinct`. - */ - attributesForFaceting?: string[]; - - /** - * Attributes to include in the API response. To reduce the size of your response, you can retrieve only some of the attributes. By default, the response includes all attributes. + * Attributes to include in the API response. To reduce the size of your response, you can retrieve only some of the attributes. - `*` 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?: string[]; /** - * Determines the order in which Algolia [returns your results](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/). + * 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?: string[]; /** - * Specifies the [Custom ranking criterion](https://www.algolia.com/doc/guides/managing-results/must-do/custom-ranking/). Use the `asc` and `desc` modifiers to specify the ranking order: ascending or descending. + * Attributes to use as [custom ranking](https://www.algolia.com/doc/guides/managing-results/must-do/custom-ranking/). The custom ranking attributes decide which items are shown first if the other ranking criteria are equal. Records with missing values for your selected custom ranking attributes are always sorted last. Boolean attributes are sorted based on their alphabetical order. **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.
If you use two or more custom ranking attributes, [reduce the precision](https://www.algolia.com/doc/guides/managing-results/must-do/custom-ranking/how-to/controlling-custom-ranking-metrics-precision/) of your first attributes, or the other attributes will never be applied. */ customRanking?: string[]; /** - * Relevancy threshold below which less relevant results aren\'t included in the results. + * 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. Strings that match the search query in the attributes are highlighted by surrounding them with HTML tags (`highlightPreTag` and `highlightPostTag`). + * Attributes to highlight. By default, all searchable attributes are highlighted. Use `*` to highlight all attributes or use an empty array `[]` to turn off highlighting. 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?: string[]; /** - * Attributes to _snippet_. \'Snippeting\' is shortening the attribute to a certain number of words. If not specified, the attribute is shortened to the 10 words around the matching string but you can specify the number. For example: `body:20`. + * Attributes for which to enable snippets. 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?: string[]; /** - * HTML string to insert before the highlighted parts in all highlight and snippet results. + * HTML tag to insert before the highlighted parts in all highlighted results and snippets. */ highlightPreTag?: string; /** - * HTML string to insert after the highlighted parts in all highlight and snippet results. + * HTML tag to insert after the highlighted parts in all highlighted results and snippets. */ highlightPostTag?: string; @@ -66,7 +61,7 @@ export type IndexSettingsAsSearchParams = { snippetEllipsisText?: string; /** - * Restrict highlighting and snippeting to items that matched the query. + * 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; @@ -76,24 +71,24 @@ export type IndexSettingsAsSearchParams = { hitsPerPage?: number; /** - * Minimum number of characters a word in the query string 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). + * 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 query string 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). + * 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 (\"numeric tokens\") in the query string. + * 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/). + * Attributes for which you want to turn off [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/). 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?: string[]; @@ -102,27 +97,27 @@ export type IndexSettingsAsSearchParams = { removeStopWords?: RemoveStopWords; /** - * Characters that the engine shouldn\'t automatically [normalize](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/normalization/). + * Characters for which diacritics should be preserved. By default, Algolia removes diacritics from letters. For example, `é` becomes `e`. If this causes issues in your search, you can specify characters that should keep their diacritics. */ keepDiacriticsOnCharacters?: string; /** - * Sets your user\'s search language. This adjusts language-specific settings and features such as `ignorePlurals`, `removeStopWords`, and [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) word detection. + * [ISO code](https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes) for language-specific settings such as plurals, stop words, 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?: string[]; /** - * [Splits compound words](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/#splitting-compound-words) into their component word parts in the query. + * Whether to split compound words 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. */ decompoundQuery?: boolean; /** - * Incidates whether [Rules](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/) are enabled. + * Whether to enable rules. */ enableRules?: boolean; /** - * Incidates whether [Personalization](https://www.algolia.com/doc/guides/personalization/what-is-personalization/) is enabled. + * Whether to enable Personalization. */ enablePersonalization?: boolean; @@ -135,51 +130,51 @@ export type IndexSettingsAsSearchParams = { semanticSearch?: SemanticSearch; /** - * Enables the [advanced query syntax](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/#advanced-syntax). + * Whether to support phrase matching and excluding words from search queries. Use the `advancedSyntaxFeatures` parameter to control which feature is supported. */ advancedSyntax?: boolean; /** - * Words which should be considered [optional](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/#creating-a-list-of-optional-words) when found in a query. + * 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 dividied 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?: string[]; /** - * 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). + * 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). This can be useful for attributes with long values, where the likelyhood 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?: string[]; exactOnSingleWordQuery?: ExactOnSingleWordQuery; /** - * Alternatives that should be considered an exact match by [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). + * 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.
. */ alternativesAsExact?: AlternativesAsExact[]; /** - * Allows you to specify which advanced syntax features are active when `advancedSyntax` is enabled. + * 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?: AdvancedSyntaxFeatures[]; distinct?: Distinct; /** - * Whether to highlight and snippet the original word that matches the synonym or the synonym itself. + * 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 occurences of \"house\" are replaced by \"home\" in the highlighted response. */ replaceSynonymsInHighlight?: boolean; /** - * Precision of the [proximity ranking criterion](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#proximity). + * 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; /** - * Attributes to include in the API response for search and browse queries. + * 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?: string[]; /** - * Maximum number of facet hits to return when [searching for facet values](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#search-for-facet-values). + * 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; @@ -189,19 +184,19 @@ export type IndexSettingsAsSearchParams = { maxValuesPerFacet?: number; /** - * Controls how facet values are fetched. + * 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; /** - * When the [Attribute criterion is ranked above Proximity](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#attribute-and-proximity-combinations) in your ranking formula, Proximity is used to select which searchable attribute is matched in the Attribute ranking stage. + * 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; /** - * Indicates whether this search will use [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking/). + * 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; diff --git a/packages/algoliasearch/lite/model/matchLevel.ts b/packages/algoliasearch/lite/model/matchLevel.ts index 771daa1fe..a5fa02991 100644 --- a/packages/algoliasearch/lite/model/matchLevel.ts +++ b/packages/algoliasearch/lite/model/matchLevel.ts @@ -1,6 +1,6 @@ // 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. /** - * Indicates how well the attribute matched the search query. + * Whether the whole query string matches or only a part. */ export type MatchLevel = 'full' | 'none' | 'partial'; diff --git a/packages/algoliasearch/lite/model/mode.ts b/packages/algoliasearch/lite/model/mode.ts index 128d51a2b..37ed88734 100644 --- a/packages/algoliasearch/lite/model/mode.ts +++ b/packages/algoliasearch/lite/model/mode.ts @@ -1,6 +1,6 @@ // 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. /** - * Search mode the index will use to query for results. + * Search mode the index will use to query for results. This setting only applies to indices, for which Algolia enabled NeuralSearch for you. */ export type Mode = 'keywordSearch' | 'neuralSearch'; diff --git a/packages/algoliasearch/lite/model/numericFilters.ts b/packages/algoliasearch/lite/model/numericFilters.ts index dde128ffc..3db0c89dc 100644 --- a/packages/algoliasearch/lite/model/numericFilters.ts +++ b/packages/algoliasearch/lite/model/numericFilters.ts @@ -3,6 +3,6 @@ import type { MixedSearchFilters } from './mixedSearchFilters'; /** - * [Filter on numeric attributes](https://www.algolia.com/doc/api-reference/api-parameters/numericFilters/). + * Filter by numeric facets. **Prefer using the `filters` parameter, which supports all filter types and combinations with boolean operators.** You can use numeric comparison operators: `<`, `<=`, `=`, `!=`, `>`, `>=`. Comparsions are precise up to 3 decimals. You can also provide ranges: `facet: TO `. The range includes the lower and upper boundaries. The same combination rules apply as for `facetFilters`. */ export type NumericFilters = MixedSearchFilters[] | string; diff --git a/packages/algoliasearch/lite/model/operationType.ts b/packages/algoliasearch/lite/model/operationType.ts index 4674a69e0..3b22cc054 100644 --- a/packages/algoliasearch/lite/model/operationType.ts +++ b/packages/algoliasearch/lite/model/operationType.ts @@ -1,6 +1,6 @@ // 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. /** - * Operation to perform (_move_ or _copy_). + * Operation to perform on the index. */ export type OperationType = 'copy' | 'move'; diff --git a/packages/algoliasearch/lite/model/optionalFilters.ts b/packages/algoliasearch/lite/model/optionalFilters.ts index 1836d9315..f910cd0cf 100644 --- a/packages/algoliasearch/lite/model/optionalFilters.ts +++ b/packages/algoliasearch/lite/model/optionalFilters.ts @@ -3,6 +3,6 @@ import type { MixedSearchFilters } from './mixedSearchFilters'; /** - * Create filters to boost or demote records. Records that match the filter are ranked higher for positive and lower for negative optional filters. In contrast to regular filters, records that don\'t match the optional filter are still included in the results, only their ranking is affected. + * Filters to promote or demote records in the search results. Optional filters work like facet filters, but they don\'t exclude records from the search results. Records that match the optional filter rank before records that don\'t match. If you\'re using a negative filter `facet:-value`, matching records rank after records that don\'t match. - Optional filters don\'t work on virtual replicas. - Optional filters are applied _after_ sort-by attributes. - Optional filters don\'t work with numeric attributes. */ export type OptionalFilters = MixedSearchFilters[] | string; diff --git a/packages/algoliasearch/lite/model/params.ts b/packages/algoliasearch/lite/model/params.ts index dff37195c..8dbd02c2f 100644 --- a/packages/algoliasearch/lite/model/params.ts +++ b/packages/algoliasearch/lite/model/params.ts @@ -5,7 +5,7 @@ import type { ConsequenceQuery } from './consequenceQuery'; import type { RenderingContent } from './renderingContent'; /** - * Additional search parameters. + * Parameters to apply to this search. You can use all search parameters, plus special `automaticFacetFilters`, `automaticOptionalFacetFilters`, and `query`. */ export type Params = { query?: ConsequenceQuery; diff --git a/packages/algoliasearch/lite/model/promoteObjectID.ts b/packages/algoliasearch/lite/model/promoteObjectID.ts index aeb5e5e29..6e2f37992 100644 --- a/packages/algoliasearch/lite/model/promoteObjectID.ts +++ b/packages/algoliasearch/lite/model/promoteObjectID.ts @@ -5,12 +5,12 @@ */ export type PromoteObjectID = { /** - * Unique identifier of the record to promote. + * Unique record identifier. */ objectID: string; /** - * The position to promote the records to. If you pass objectIDs, the records are placed at this position as a group. For example, if you pronmote four objectIDs to position 0, the records take the first four positions. + * Position in the search results where you want to show the promoted records. */ position: number; }; diff --git a/packages/algoliasearch/lite/model/promoteObjectIDs.ts b/packages/algoliasearch/lite/model/promoteObjectIDs.ts index cfdaa6d76..01a5dd576 100644 --- a/packages/algoliasearch/lite/model/promoteObjectIDs.ts +++ b/packages/algoliasearch/lite/model/promoteObjectIDs.ts @@ -5,12 +5,12 @@ */ export type PromoteObjectIDs = { /** - * Unique identifiers of the records to promote. + * Object IDs of the records you want to promote. The records are placed as a group at the `position`. For example, if you want to promote four records to position `0`, they will be the first four search results. */ objectIDs: string[]; /** - * The position to promote the records to. If you pass objectIDs, the records are placed at this position as a group. For example, if you pronmote four objectIDs to position 0, the records take the first four positions. + * Position in the search results where you want to show the promoted records. */ position: number; }; diff --git a/packages/algoliasearch/lite/model/queryType.ts b/packages/algoliasearch/lite/model/queryType.ts index 50424749d..a609aca0e 100644 --- a/packages/algoliasearch/lite/model/queryType.ts +++ b/packages/algoliasearch/lite/model/queryType.ts @@ -1,6 +1,6 @@ // 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. /** - * Determines how query words are [interpreted as prefixes](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/in-depth/prefix-searching/). + * Determines if and how query words are interpreted as prefixes. By default, only the last query word is treated as prefix (`prefixLast`). To turn off prefix search, use `prefixNone`. Avoid `prefixAll`, which treats all query words as prefixes. This might lead to counterintuitive results and makes your search slower. For more information, see [Prefix searching](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/in-depth/prefix-searching/). */ export type QueryType = 'prefixAll' | 'prefixLast' | 'prefixNone'; diff --git a/packages/algoliasearch/lite/model/rankingInfo.ts b/packages/algoliasearch/lite/model/rankingInfo.ts index 71de0b00e..14edcdc59 100644 --- a/packages/algoliasearch/lite/model/rankingInfo.ts +++ b/packages/algoliasearch/lite/model/rankingInfo.ts @@ -3,14 +3,17 @@ import type { MatchedGeoLocation } from './matchedGeoLocation'; import type { Personalization } from './personalization'; +/** + * Object with detailed information about the record\'s ranking. + */ export type RankingInfo = { /** - * This field is reserved for advanced usage. + * Whether a filter matched the query. */ filters: number; /** - * Position of the most important matched attribute in the attributes to index list. + * Position of the first matched word in the best matching attribute of the record. */ firstMatchedWord: number; @@ -39,27 +42,27 @@ export type RankingInfo = { nbTypos: number; /** - * Present and set to true if a Rule promoted the hit. + * Whether the record was promoted by a rule. */ promoted: boolean; /** - * When the query contains more than one word, the sum of the distances between matched words (in meters). + * Number of words between multiple matches in the query plus 1. For single word queries, `proximityDistance` is 0. */ proximityDistance?: number; /** - * Custom ranking for the object, expressed as a single integer value. + * Overall ranking of the record, expressed as a single integer. This attribute is internal. */ userScore: number; /** - * Number of matched words, including prefixes and typos. + * Number of matched words. */ words: number; /** - * Wether the record are promoted by the re-ranking strategy. + * Whether the record is re-ranked. */ promotedByReRanking?: boolean; }; diff --git a/packages/algoliasearch/lite/model/reRankingApplyFilter.ts b/packages/algoliasearch/lite/model/reRankingApplyFilter.ts index 02a02545f..ced0223fd 100644 --- a/packages/algoliasearch/lite/model/reRankingApplyFilter.ts +++ b/packages/algoliasearch/lite/model/reRankingApplyFilter.ts @@ -3,6 +3,6 @@ import type { MixedSearchFilters } from './mixedSearchFilters'; /** - * When [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking/) is enabled, only records that match these filters will be affected by Dynamic Re-Ranking. + * Restrict [Dynamic Re-ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking/) to records that match these filters. */ export type ReRankingApplyFilter = MixedSearchFilters[] | string; diff --git a/packages/algoliasearch/lite/model/removeStopWords.ts b/packages/algoliasearch/lite/model/removeStopWords.ts index 33f66341c..9bdbf9176 100644 --- a/packages/algoliasearch/lite/model/removeStopWords.ts +++ b/packages/algoliasearch/lite/model/removeStopWords.ts @@ -1,6 +1,6 @@ // 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. /** - * Removes stop (common) words from the query before executing it. `removeStopWords` is used in conjunction with the `queryLanguages` setting. _list_: language ISO codes for which stop words should be enabled. This list will override any values that you may have set in `queryLanguages`. _true_: enables the stop words feature, ensuring that stop words are removed from consideration in a search. The languages supported here are either [every language](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages/) (this is the default) or those set by `queryLanguages`. _false_: turns off the stop words feature, allowing stop words to be taken into account in a search. + * Removes stop words from the search query. Stop words are common words like articles, conjunctions, prepositions, or pronouns that have little or no meaning on their own. In English, \"the\", \"a\", or \"and\" are stop words. You should only use this feature for the languages used in your index. */ export type RemoveStopWords = string[] | boolean; diff --git a/packages/algoliasearch/lite/model/removeWordsIfNoResults.ts b/packages/algoliasearch/lite/model/removeWordsIfNoResults.ts index 2e5b6bdef..81519af90 100644 --- a/packages/algoliasearch/lite/model/removeWordsIfNoResults.ts +++ b/packages/algoliasearch/lite/model/removeWordsIfNoResults.ts @@ -1,7 +1,7 @@ // 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. /** - * Strategy to [remove words](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/in-depth/why-use-remove-words-if-no-results/) from the query when it doesn\'t match any hits. + * Strategy for removing words from the query when it doesn\'t return any results. This helps to avoid returning empty search results.
none
No words are removed when a query doesn\'t return results.
lastWords
Treat the last (then second to last, then third to last) word as optional, until there are results or at most 5 words have been removed.
firstWords
Treat the first (then second, then third) word as optional, until there are results or at most 5 words have been removed.
allOptional
Treat all words as optional.
For more information, see [Remove words to improve results](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/in-depth/why-use-remove-words-if-no-results/). */ export type RemoveWordsIfNoResults = | 'allOptional' diff --git a/packages/algoliasearch/lite/model/renderingContent.ts b/packages/algoliasearch/lite/model/renderingContent.ts index 9c632b96e..4385efd64 100644 --- a/packages/algoliasearch/lite/model/renderingContent.ts +++ b/packages/algoliasearch/lite/model/renderingContent.ts @@ -3,7 +3,7 @@ import type { FacetOrdering } from './facetOrdering'; /** - * Extra content for the search UI, for example, to control the [ordering and display of facets](https://www.algolia.com/doc/guides/managing-results/rules/merchandising-and-promoting/how-to/merchandising-facets/#merchandise-facets-and-their-values-in-the-manual-editor). You can set a default value and dynamically override it with [Rules](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/). + * Extra data that can be used in the search UI. You can use this to control aspects of your search UI, such as, the order of facet names and values without changing your frontend code. */ export type RenderingContent = { facetOrdering?: FacetOrdering; diff --git a/packages/algoliasearch/lite/model/rule.ts b/packages/algoliasearch/lite/model/rule.ts index 77a961294..b002ec88a 100644 --- a/packages/algoliasearch/lite/model/rule.ts +++ b/packages/algoliasearch/lite/model/rule.ts @@ -9,29 +9,29 @@ import type { TimeRange } from './timeRange'; */ export type Rule = { /** - * Unique identifier for a rule object. + * Unique identifier of a rule object. */ objectID: string; /** - * [Conditions](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/#conditions) required to activate a rule. You can use up to 25 conditions per rule. + * Conditions that trigger a rule. Some consequences require specific conditions or don\'t require any condition. For more information, see [Conditions](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/#conditions). */ conditions?: Condition[]; consequence?: Consequence; /** - * Description of the rule\'s purpose. This can be helpful for display in the Algolia dashboard. + * Description of the rule\'s purpose to help you distinguish between different rules. */ description?: string; /** - * Indicates whether to enable the rule. If it isn\'t enabled, it isn\'t applied at query time. + * Whether the rule is active. */ enabled?: boolean; /** - * If you specify a validity period, the rule _only_ applies only during that period. If specified, the array must not be empty. + * Time periods when the rule is active. */ validity?: TimeRange[]; }; diff --git a/packages/algoliasearch/lite/model/searchDictionaryEntriesResponse.ts b/packages/algoliasearch/lite/model/searchDictionaryEntriesResponse.ts new file mode 100644 index 000000000..88880a028 --- /dev/null +++ b/packages/algoliasearch/lite/model/searchDictionaryEntriesResponse.ts @@ -0,0 +1,25 @@ +// 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 { DictionaryEntry } from './dictionaryEntry'; + +export type SearchDictionaryEntriesResponse = { + /** + * Dictionary entries matching the search criteria. + */ + hits: DictionaryEntry[]; + + /** + * Requested page of the API response. + */ + page: number; + + /** + * Number of results (hits). + */ + nbHits: number; + + /** + * Number of pages of results. + */ + nbPages: number; +}; diff --git a/packages/algoliasearch/lite/model/searchForFacetValuesResponse.ts b/packages/algoliasearch/lite/model/searchForFacetValuesResponse.ts index a842add7b..32a0189e7 100644 --- a/packages/algoliasearch/lite/model/searchForFacetValuesResponse.ts +++ b/packages/algoliasearch/lite/model/searchForFacetValuesResponse.ts @@ -3,6 +3,9 @@ import type { FacetHits } from './facetHits'; export type SearchForFacetValuesResponse = { + /** + * Matching facet values. + */ facetHits: FacetHits[]; /** diff --git a/packages/algoliasearch/lite/model/searchForFacetsOptions.ts b/packages/algoliasearch/lite/model/searchForFacetsOptions.ts index 68d26be39..d599af5dc 100644 --- a/packages/algoliasearch/lite/model/searchForFacetsOptions.ts +++ b/packages/algoliasearch/lite/model/searchForFacetsOptions.ts @@ -9,7 +9,7 @@ export type SearchForFacetsOptions = { facet: string; /** - * Algolia index name. + * Index name. */ indexName: string; @@ -19,7 +19,7 @@ export type SearchForFacetsOptions = { facetQuery?: string; /** - * Maximum number of facet hits to return when [searching for facet values](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#search-for-facet-values). + * 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; diff --git a/packages/algoliasearch/lite/model/searchForHitsOptions.ts b/packages/algoliasearch/lite/model/searchForHitsOptions.ts index f75300dbc..08edcf846 100644 --- a/packages/algoliasearch/lite/model/searchForHitsOptions.ts +++ b/packages/algoliasearch/lite/model/searchForHitsOptions.ts @@ -4,7 +4,7 @@ import type { SearchTypeDefault } from './searchTypeDefault'; export type SearchForHitsOptions = { /** - * Algolia index name. + * Index name. */ indexName: string; diff --git a/packages/algoliasearch/lite/model/searchHits.ts b/packages/algoliasearch/lite/model/searchHits.ts index 8826d69fb..13dafbaba 100644 --- a/packages/algoliasearch/lite/model/searchHits.ts +++ b/packages/algoliasearch/lite/model/searchHits.ts @@ -3,10 +3,13 @@ import type { Hit } from './hit'; export type SearchHits> = Record & { + /** + * Search results (hits). Hits are records from your index that match the search criteria, augmented with additional attributes, such as, for highlighting. + */ hits: Array>; /** - * Text to search for in an index. + * Search query. */ query: string; diff --git a/packages/algoliasearch/lite/model/searchParamsQuery.ts b/packages/algoliasearch/lite/model/searchParamsQuery.ts index 39058cbe1..9f1926f6c 100644 --- a/packages/algoliasearch/lite/model/searchParamsQuery.ts +++ b/packages/algoliasearch/lite/model/searchParamsQuery.ts @@ -2,7 +2,7 @@ export type SearchParamsQuery = { /** - * Text to search for in an index. + * Search query. */ query?: string; }; diff --git a/packages/algoliasearch/lite/model/searchStrategy.ts b/packages/algoliasearch/lite/model/searchStrategy.ts index 84d4ae8be..1bda46977 100644 --- a/packages/algoliasearch/lite/model/searchStrategy.ts +++ b/packages/algoliasearch/lite/model/searchStrategy.ts @@ -1,6 +1,6 @@ // 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. /** - * - `none`: executes all queries. - `stopIfEnoughMatches`: executes queries one by one, stopping further query execution as soon as a query matches at least the `hitsPerPage` number of results. + * Strategy for multiple search queries: - `none`. Run all queries. - `stopIfEnoughMatches`. Run the queries one by one, stopping as soon as a query matches at least the `hitsPerPage` number of results. */ export type SearchStrategy = 'none' | 'stopIfEnoughMatches'; diff --git a/packages/algoliasearch/lite/model/searchSynonymsResponse.ts b/packages/algoliasearch/lite/model/searchSynonymsResponse.ts index ac9e1a4a4..cef9b724f 100644 --- a/packages/algoliasearch/lite/model/searchSynonymsResponse.ts +++ b/packages/algoliasearch/lite/model/searchSynonymsResponse.ts @@ -4,12 +4,12 @@ import type { SynonymHit } from './synonymHit'; export type SearchSynonymsResponse = Record & { /** - * Synonym objects. + * Matching synonyms. */ hits: SynonymHit[]; /** - * Number of hits the search query matched. + * Number of results (hits). */ nbHits: number; }; diff --git a/packages/algoliasearch/lite/model/securedAPIKeyRestrictions.ts b/packages/algoliasearch/lite/model/securedAPIKeyRestrictions.ts index bba07db28..c230dee7d 100644 --- a/packages/algoliasearch/lite/model/securedAPIKeyRestrictions.ts +++ b/packages/algoliasearch/lite/model/securedAPIKeyRestrictions.ts @@ -6,27 +6,27 @@ export type SecuredAPIKeyRestrictions = { searchParams?: SearchParamsObject; /** - * Filters that apply to every search made with the secured API key. You can add extra filters at search time with the filters query parameter. For example, if you set the filter group:admin on your generated API key, and you add groups:press OR groups:visitors with the filters query parameter, your final search filter is equivalent to groups:admin AND (groups:press OR groups:visitors). + * Filters that apply to every search made with the secured API key. Extra filters added at search time will be combined with `AND`. For example, if you set `group:admin` as fixed filter on your generated API key, and add `groups:visitors` to the search query, the complete set of filters will be `group:admin AND groups:visitors`. */ filters?: string; /** - * Unix timestamp used to set the expiration date of the API key. + * Timestamp in [Unix epoch time](https://en.wikipedia.org/wiki/Unix_time) when the API key should expire. */ validUntil?: number; /** - * Index names that can be queried. + * Index names or patterns that this API key can access. By default, an API key can access all indices in the same application. You can use leading and trailing wildcard characters (`*`): - `dev_*` matches all indices starting with \"dev_\". - `*_dev` matches all indices ending with \"_dev\". - `*_products_*` matches all indices containing \"_products_\". */ restrictIndices?: string[]; /** - * IPv4 network allowed to use the generated key. Use this to protect against API key leaking and reuse. You can only provide a single source, but you can specify a range of IPs (for example, 192.168.1.0/24). + * IP network that are allowed to use this key. You can only add a single source, but you can provide a range of IP addresses. Use this to protect against API key leaking and reuse. */ restrictSources?: string; /** - * Unique user IP address. This can be useful when you want to impose a rate limit on specific users. By default, rate limits are set based on the IP address. This can become an issue when several users search from the same IP address. To avoid this, you can set a unique userToken for each user when generating their API key. This lets you restrict each user to a maximum number of API calls per hour, even if they share their IP with another user. Specifying the userToken in a secured API key is also a good security practice as it ensures users don\'t change it. Many features like Analytics, Personalization, and Dynamic Re-ranking rely on the authenticity of user identifiers. Setting the userToken at the API key level ensures that downstream services work as expected and prevents abuse. + * Pseudonymous user identifier to restrict usage of this API key to specific users. By default, rate limits are set based on IP addresses. This can be an issue if many users search from the same IP address. To avoid this, add a user token to each generated API key. */ userToken?: string; }; diff --git a/packages/algoliasearch/lite/model/semanticSearch.ts b/packages/algoliasearch/lite/model/semanticSearch.ts index c9b832249..86cfd43a0 100644 --- a/packages/algoliasearch/lite/model/semanticSearch.ts +++ b/packages/algoliasearch/lite/model/semanticSearch.ts @@ -1,11 +1,11 @@ // 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. /** - * Settings for the semantic search part of NeuralSearch. Only used when `mode` is _neuralSearch_. + * Settings for the semantic search part of NeuralSearch. Only used when `mode` is `neuralSearch`. */ export type SemanticSearch = { /** - * Indices from which to collect click and conversion events. If null, the current index and replica group will be used as the event source. + * Indices from which to collect click and conversion events. If null, the current index and all its replicas are used. */ eventSources?: string[] | null; }; diff --git a/packages/algoliasearch/lite/model/snippetResultOption.ts b/packages/algoliasearch/lite/model/snippetResultOption.ts index cb21bd0f6..daab65f2d 100644 --- a/packages/algoliasearch/lite/model/snippetResultOption.ts +++ b/packages/algoliasearch/lite/model/snippetResultOption.ts @@ -3,11 +3,11 @@ import type { MatchLevel } from './matchLevel'; /** - * Snippeted attributes show parts of the matched attributes. Only returned when attributesToSnippet is non-empty. + * Snippets that show the context around a matching search query. */ export type SnippetResultOption = { /** - * Markup text with `facetQuery` matches highlighted. + * Highlighted attribute value, including HTML tags. */ value: string; diff --git a/packages/algoliasearch/lite/model/sortRemainingBy.ts b/packages/algoliasearch/lite/model/sortRemainingBy.ts index a5faf046e..7da7c289e 100644 --- a/packages/algoliasearch/lite/model/sortRemainingBy.ts +++ b/packages/algoliasearch/lite/model/sortRemainingBy.ts @@ -1,6 +1,6 @@ // 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. /** - * How to display the remaining items: - `count`: facet count (descending). - `alpha`: alphabetical (ascending). - `hidden`: show only pinned values. + * Order of facet values that aren\'t explicitly positioned with the `order` setting.
count
Order remaining facet values by decreasing count. The count is the number of matching records containing this facet value.
alpha
Sort facet values alphabetically.
hidden
Don\'t show facet values that aren\'t explicitly positioned.
. */ export type SortRemainingBy = 'alpha' | 'count' | 'hidden'; diff --git a/packages/algoliasearch/lite/model/tagFilters.ts b/packages/algoliasearch/lite/model/tagFilters.ts index 1b7e964bd..966082364 100644 --- a/packages/algoliasearch/lite/model/tagFilters.ts +++ b/packages/algoliasearch/lite/model/tagFilters.ts @@ -3,6 +3,6 @@ import type { MixedSearchFilters } from './mixedSearchFilters'; /** - * [Filter hits by tags](https://www.algolia.com/doc/api-reference/api-parameters/tagFilters/). + * Filter the search by values of the special `_tags` attribute. **Prefer using the `filters` parameter, which supports all filter types and combinations with boolean operators.** Different from regular facets, `_tags` can only be used for filtering (including or excluding records). You won\'t get a facet count. The same combination and escaping rules apply as for `facetFilters`. */ export type TagFilters = MixedSearchFilters[] | string; diff --git a/packages/algoliasearch/lite/model/taskStatus.ts b/packages/algoliasearch/lite/model/taskStatus.ts index 8f335ad21..169dd7bf2 100644 --- a/packages/algoliasearch/lite/model/taskStatus.ts +++ b/packages/algoliasearch/lite/model/taskStatus.ts @@ -1,6 +1,6 @@ // 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. /** - * _published_ if the task has been processed, _notPublished_ otherwise. + * Task status, `published` if the task is completed, `notPublished` otherwise. */ export type TaskStatus = 'notPublished' | 'published'; diff --git a/packages/algoliasearch/lite/model/timeRange.ts b/packages/algoliasearch/lite/model/timeRange.ts index cfd663c8a..dee6043c9 100644 --- a/packages/algoliasearch/lite/model/timeRange.ts +++ b/packages/algoliasearch/lite/model/timeRange.ts @@ -2,12 +2,12 @@ export type TimeRange = { /** - * Lower bound of the time range (Unix timestamp). + * When the rule should start to be active, in Unix epoch time. */ from: number; /** - * Upper bound of the time range (Unix timestamp). + * When the rule should stop to be active, in Unix epoch time. */ until: number; }; diff --git a/packages/algoliasearch/lite/model/typoTolerance.ts b/packages/algoliasearch/lite/model/typoTolerance.ts index 58ae716ef..0bd64036f 100644 --- a/packages/algoliasearch/lite/model/typoTolerance.ts +++ b/packages/algoliasearch/lite/model/typoTolerance.ts @@ -3,6 +3,6 @@ import type { TypoToleranceEnum } from './typoToleranceEnum'; /** - * Controls whether [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/) is enabled and how it is applied. + * Whether [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/) is enabled and how it is applied. If typo tolerance is true, `min`, or `strict`, [word splitting and concetenation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/splitting-and-concatenation/) is also active. */ export type TypoTolerance = TypoToleranceEnum | boolean; diff --git a/packages/algoliasearch/lite/model/typoToleranceEnum.ts b/packages/algoliasearch/lite/model/typoToleranceEnum.ts index 05cf7b62d..a33877b0d 100644 --- a/packages/algoliasearch/lite/model/typoToleranceEnum.ts +++ b/packages/algoliasearch/lite/model/typoToleranceEnum.ts @@ -1,3 +1,6 @@ // 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. +/** + * - `min`. Return matches with the lowest number of typos. For example, if you have matches without typos, only include those. But if there are no matches without typos (with 1 typo), include matches with 1 typo (2 typos). - `strict`. Return matches with the two lowest numbers of typos. With `strict`, the Typo ranking criterion is applied first in the `ranking` setting. + */ export type TypoToleranceEnum = 'min' | 'strict'; diff --git a/packages/algoliasearch/lite/model/updatedRuleResponse.ts b/packages/algoliasearch/lite/model/updatedRuleResponse.ts index 9e445c836..2a2b24689 100644 --- a/packages/algoliasearch/lite/model/updatedRuleResponse.ts +++ b/packages/algoliasearch/lite/model/updatedRuleResponse.ts @@ -2,7 +2,7 @@ export type UpdatedRuleResponse = { /** - * Unique object identifier. + * Unique identifier of a rule object. */ objectID: string; @@ -12,7 +12,7 @@ export type UpdatedRuleResponse = { updatedAt: string; /** - * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the `task` operation and this `taskID`. + * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the [`task` operation](#tag/Indices/operation/getTask) and this `taskID`. */ taskID: number; }; diff --git a/packages/algoliasearch/lite/model/userId.ts b/packages/algoliasearch/lite/model/userId.ts index 731250edc..e46823f8a 100644 --- a/packages/algoliasearch/lite/model/userId.ts +++ b/packages/algoliasearch/lite/model/userId.ts @@ -5,7 +5,7 @@ */ export type UserId = { /** - * UserID of the user. + * User ID. */ userID: string; diff --git a/packages/algoliasearch/lite/model/value.ts b/packages/algoliasearch/lite/model/value.ts index 9bbf488f6..9054c5e5d 100644 --- a/packages/algoliasearch/lite/model/value.ts +++ b/packages/algoliasearch/lite/model/value.ts @@ -4,7 +4,7 @@ import type { SortRemainingBy } from './sortRemainingBy'; export type Value = { /** - * Pinned order of facet lists. + * Explicit order of facets or facet values. This setting lets you always show specific facets or facet values at the top of the list. */ order?: string[]; diff --git a/packages/algoliasearch/lite/src/liteClient.ts b/packages/algoliasearch/lite/src/liteClient.ts index befdc0fdf..4cc632dc3 100644 --- a/packages/algoliasearch/lite/src/liteClient.ts +++ b/packages/algoliasearch/lite/src/liteClient.ts @@ -157,12 +157,12 @@ export function createLiteClient({ }, /** - * Send multiple search queries to one or more indices. + * Sends multiple search request to one or more indices. This can be useful in these cases: - Different indices for different purposes, such as, one index for products, another one for marketing content. - Multiple searches to the same index—for example, with different filters. * * Required API Key ACLs: * - search. * - * @param searchMethodParams - Query requests and strategies. Results will be received in the same order as the queries. + * @param searchMethodParams - Muli-search request body. Results are returned in the same order as the requests. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ search( diff --git a/packages/client-abtesting/model/aBTestResponse.ts b/packages/client-abtesting/model/aBTestResponse.ts index 359b08b95..37a1535ce 100644 --- a/packages/client-abtesting/model/aBTestResponse.ts +++ b/packages/client-abtesting/model/aBTestResponse.ts @@ -12,7 +12,7 @@ export type ABTestResponse = { abTestID: number; /** - * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the `task` operation and this `taskID`. + * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the [`task` operation](#tag/Indices/operation/getTask) and this `taskID`. */ taskID: number; }; diff --git a/packages/client-abtesting/model/clientMethodProps.ts b/packages/client-abtesting/model/clientMethodProps.ts index cf497bff6..4b58cd01f 100644 --- a/packages/client-abtesting/model/clientMethodProps.ts +++ b/packages/client-abtesting/model/clientMethodProps.ts @@ -89,11 +89,11 @@ export type GetABTestProps = { */ export type ListABTestsProps = { /** - * Position of the starting record. Used for paging. 0 is the first record. + * Position of the first item to return. */ offset?: number; /** - * Number of records to return (page size). + * Number of items to return. */ limit?: number; /** diff --git a/packages/client-abtesting/src/abtestingClient.ts b/packages/client-abtesting/src/abtestingClient.ts index 74993eacb..c436e506f 100644 --- a/packages/client-abtesting/src/abtestingClient.ts +++ b/packages/client-abtesting/src/abtestingClient.ts @@ -367,8 +367,8 @@ export function createAbtestingClient({ * - analytics. * * @param listABTests - The listABTests object. - * @param listABTests.offset - Position of the starting record. Used for paging. 0 is the first record. - * @param listABTests.limit - Number of records to return (page size). + * @param listABTests.offset - Position of the first item to return. + * @param listABTests.limit - Number of items to return. * @param listABTests.indexPrefix - Only return A/B tests for indices starting with this prefix. * @param listABTests.indexSuffix - Only return A/B tests for indices ending with this suffix. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. diff --git a/packages/client-analytics/model/clientMethodProps.ts b/packages/client-analytics/model/clientMethodProps.ts index b2cbc6f50..2c813a826 100644 --- a/packages/client-analytics/model/clientMethodProps.ts +++ b/packages/client-analytics/model/clientMethodProps.ts @@ -72,15 +72,15 @@ export type CustomPutProps = { */ export type GetAverageClickPositionProps = { /** - * Index name to target. + * Index name. */ index: string; /** - * Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * Start date (`YYYY-MM-DD`) of the period to analyze. */ startDate?: string; /** - * End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * End date (`YYYY-MM-DD`) of the period to analyze. */ endDate?: string; /** @@ -94,15 +94,15 @@ export type GetAverageClickPositionProps = { */ export type GetClickPositionsProps = { /** - * Index name to target. + * Index name. */ index: string; /** - * Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * Start date (`YYYY-MM-DD`) of the period to analyze. */ startDate?: string; /** - * End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * End date (`YYYY-MM-DD`) of the period to analyze. */ endDate?: string; /** @@ -116,15 +116,15 @@ export type GetClickPositionsProps = { */ export type GetClickThroughRateProps = { /** - * Index name to target. + * Index name. */ index: string; /** - * Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * Start date (`YYYY-MM-DD`) of the period to analyze. */ startDate?: string; /** - * End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * End date (`YYYY-MM-DD`) of the period to analyze. */ endDate?: string; /** @@ -138,15 +138,15 @@ export type GetClickThroughRateProps = { */ export type GetConversationRateProps = { /** - * Index name to target. + * Index name. */ index: string; /** - * Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * Start date (`YYYY-MM-DD`) of the period to analyze. */ startDate?: string; /** - * End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * End date (`YYYY-MM-DD`) of the period to analyze. */ endDate?: string; /** @@ -160,15 +160,15 @@ export type GetConversationRateProps = { */ export type GetNoClickRateProps = { /** - * Index name to target. + * Index name. */ index: string; /** - * Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * Start date (`YYYY-MM-DD`) of the period to analyze. */ startDate?: string; /** - * End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * End date (`YYYY-MM-DD`) of the period to analyze. */ endDate?: string; /** @@ -182,15 +182,15 @@ export type GetNoClickRateProps = { */ export type GetNoResultsRateProps = { /** - * Index name to target. + * Index name. */ index: string; /** - * Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * Start date (`YYYY-MM-DD`) of the period to analyze. */ startDate?: string; /** - * End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * End date (`YYYY-MM-DD`) of the period to analyze. */ endDate?: string; /** @@ -204,15 +204,15 @@ export type GetNoResultsRateProps = { */ export type GetSearchesCountProps = { /** - * Index name to target. + * Index name. */ index: string; /** - * Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * Start date (`YYYY-MM-DD`) of the period to analyze. */ startDate?: string; /** - * End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * End date (`YYYY-MM-DD`) of the period to analyze. */ endDate?: string; /** @@ -226,23 +226,23 @@ export type GetSearchesCountProps = { */ export type GetSearchesNoClicksProps = { /** - * Index name to target. + * Index name. */ index: string; /** - * Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * Start date (`YYYY-MM-DD`) of the period to analyze. */ startDate?: string; /** - * End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * End date (`YYYY-MM-DD`) of the period to analyze. */ endDate?: string; /** - * Number of records to return (page size). + * Number of items to return. */ limit?: number; /** - * Position of the starting record. Used for paging. 0 is the first record. + * Position of the first item to return. */ offset?: number; /** @@ -256,23 +256,23 @@ export type GetSearchesNoClicksProps = { */ export type GetSearchesNoResultsProps = { /** - * Index name to target. + * Index name. */ index: string; /** - * Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * Start date (`YYYY-MM-DD`) of the period to analyze. */ startDate?: string; /** - * End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * End date (`YYYY-MM-DD`) of the period to analyze. */ endDate?: string; /** - * Number of records to return (page size). + * Number of items to return. */ limit?: number; /** - * Position of the starting record. Used for paging. 0 is the first record. + * Position of the first item to return. */ offset?: number; /** @@ -286,7 +286,7 @@ export type GetSearchesNoResultsProps = { */ export type GetStatusProps = { /** - * Index name to target. + * Index name. */ index: string; }; @@ -296,23 +296,23 @@ export type GetStatusProps = { */ export type GetTopCountriesProps = { /** - * Index name to target. + * Index name. */ index: string; /** - * Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * Start date (`YYYY-MM-DD`) of the period to analyze. */ startDate?: string; /** - * End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * End date (`YYYY-MM-DD`) of the period to analyze. */ endDate?: string; /** - * Number of records to return (page size). + * Number of items to return. */ limit?: number; /** - * Position of the starting record. Used for paging. 0 is the first record. + * Position of the first item to return. */ offset?: number; /** @@ -326,7 +326,7 @@ export type GetTopCountriesProps = { */ export type GetTopFilterAttributesProps = { /** - * Index name to target. + * Index name. */ index: string; /** @@ -334,19 +334,19 @@ export type GetTopFilterAttributesProps = { */ search?: string; /** - * Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * Start date (`YYYY-MM-DD`) of the period to analyze. */ startDate?: string; /** - * End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * End date (`YYYY-MM-DD`) of the period to analyze. */ endDate?: string; /** - * Number of records to return (page size). + * Number of items to return. */ limit?: number; /** - * Position of the starting record. Used for paging. 0 is the first record. + * Position of the first item to return. */ offset?: number; /** @@ -364,7 +364,7 @@ export type GetTopFilterForAttributeProps = { */ attribute: string; /** - * Index name to target. + * Index name. */ index: string; /** @@ -372,19 +372,19 @@ export type GetTopFilterForAttributeProps = { */ search?: string; /** - * Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * Start date (`YYYY-MM-DD`) of the period to analyze. */ startDate?: string; /** - * End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * End date (`YYYY-MM-DD`) of the period to analyze. */ endDate?: string; /** - * Number of records to return (page size). + * Number of items to return. */ limit?: number; /** - * Position of the starting record. Used for paging. 0 is the first record. + * Position of the first item to return. */ offset?: number; /** @@ -398,7 +398,7 @@ export type GetTopFilterForAttributeProps = { */ export type GetTopFiltersNoResultsProps = { /** - * Index name to target. + * Index name. */ index: string; /** @@ -406,19 +406,19 @@ export type GetTopFiltersNoResultsProps = { */ search?: string; /** - * Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * Start date (`YYYY-MM-DD`) of the period to analyze. */ startDate?: string; /** - * End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * End date (`YYYY-MM-DD`) of the period to analyze. */ endDate?: string; /** - * Number of records to return (page size). + * Number of items to return. */ limit?: number; /** - * Position of the starting record. Used for paging. 0 is the first record. + * Position of the first item to return. */ offset?: number; /** @@ -432,7 +432,7 @@ export type GetTopFiltersNoResultsProps = { */ export type GetTopHitsProps = { /** - * Index name to target. + * Index name. */ index: string; /** @@ -444,19 +444,19 @@ export type GetTopHitsProps = { */ clickAnalytics?: boolean; /** - * Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * Start date (`YYYY-MM-DD`) of the period to analyze. */ startDate?: string; /** - * End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * End date (`YYYY-MM-DD`) of the period to analyze. */ endDate?: string; /** - * Number of records to return (page size). + * Number of items to return. */ limit?: number; /** - * Position of the starting record. Used for paging. 0 is the first record. + * Position of the first item to return. */ offset?: number; /** @@ -470,7 +470,7 @@ export type GetTopHitsProps = { */ export type GetTopSearchesProps = { /** - * Index name to target. + * Index name. */ index: string; /** @@ -478,11 +478,11 @@ export type GetTopSearchesProps = { */ clickAnalytics?: boolean; /** - * Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * Start date (`YYYY-MM-DD`) of the period to analyze. */ startDate?: string; /** - * End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * End date (`YYYY-MM-DD`) of the period to analyze. */ endDate?: string; /** @@ -494,11 +494,11 @@ export type GetTopSearchesProps = { */ direction?: Direction; /** - * Number of records to return (page size). + * Number of items to return. */ limit?: number; /** - * Position of the starting record. Used for paging. 0 is the first record. + * Position of the first item to return. */ offset?: number; /** @@ -512,15 +512,15 @@ export type GetTopSearchesProps = { */ export type GetUsersCountProps = { /** - * Index name to target. + * Index name. */ index: string; /** - * Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * Start date (`YYYY-MM-DD`) of the period to analyze. */ startDate?: string; /** - * End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * End date (`YYYY-MM-DD`) of the period to analyze. */ endDate?: string; /** diff --git a/packages/client-analytics/model/searchNoResultEvent.ts b/packages/client-analytics/model/searchNoResultEvent.ts index 5f2828f09..accd2bded 100644 --- a/packages/client-analytics/model/searchNoResultEvent.ts +++ b/packages/client-analytics/model/searchNoResultEvent.ts @@ -12,7 +12,7 @@ export type SearchNoResultEvent = { count: number; /** - * Number of hits the search query matched. + * Number of results (hits). */ nbHits: number; }; diff --git a/packages/client-analytics/model/topSearch.ts b/packages/client-analytics/model/topSearch.ts index 74a95fcc7..623fd8318 100644 --- a/packages/client-analytics/model/topSearch.ts +++ b/packages/client-analytics/model/topSearch.ts @@ -12,7 +12,7 @@ export type TopSearch = { count: number; /** - * Number of hits the search query matched. + * Number of results (hits). */ nbHits: number; }; diff --git a/packages/client-analytics/model/topSearchWithAnalytics.ts b/packages/client-analytics/model/topSearchWithAnalytics.ts index b5fb8c79e..bc4d3a570 100644 --- a/packages/client-analytics/model/topSearchWithAnalytics.ts +++ b/packages/client-analytics/model/topSearchWithAnalytics.ts @@ -42,7 +42,7 @@ export type TopSearchWithAnalytics = { conversionCount: number; /** - * Number of hits the search query matched. + * Number of results (hits). */ nbHits: number; }; diff --git a/packages/client-analytics/src/analyticsClient.ts b/packages/client-analytics/src/analyticsClient.ts index 42d2ac5ec..43685c816 100644 --- a/packages/client-analytics/src/analyticsClient.ts +++ b/packages/client-analytics/src/analyticsClient.ts @@ -271,9 +271,9 @@ export function createAnalyticsClient({ * - analytics. * * @param getAverageClickPosition - The getAverageClickPosition object. - * @param getAverageClickPosition.index - Index name to target. - * @param getAverageClickPosition.startDate - Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getAverageClickPosition.endDate - End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * @param getAverageClickPosition.index - Index name. + * @param getAverageClickPosition.startDate - Start date (`YYYY-MM-DD`) of the period to analyze. + * @param getAverageClickPosition.endDate - End date (`YYYY-MM-DD`) of the period to analyze. * @param getAverageClickPosition.tags - Filter analytics on the [`analyticsTags`](https://www.algolia.com/doc/api-reference/api-parameters/analyticsTags/) set at search time. Multiple tags can be combined with the operators OR and AND. If a tag contains characters like spaces or parentheses, it must be URL-encoded. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -324,9 +324,9 @@ export function createAnalyticsClient({ * - analytics. * * @param getClickPositions - The getClickPositions object. - * @param getClickPositions.index - Index name to target. - * @param getClickPositions.startDate - Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getClickPositions.endDate - End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * @param getClickPositions.index - Index name. + * @param getClickPositions.startDate - Start date (`YYYY-MM-DD`) of the period to analyze. + * @param getClickPositions.endDate - End date (`YYYY-MM-DD`) of the period to analyze. * @param getClickPositions.tags - Filter analytics on the [`analyticsTags`](https://www.algolia.com/doc/api-reference/api-parameters/analyticsTags/) set at search time. Multiple tags can be combined with the operators OR and AND. If a tag contains characters like spaces or parentheses, it must be URL-encoded. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -377,9 +377,9 @@ export function createAnalyticsClient({ * - analytics. * * @param getClickThroughRate - The getClickThroughRate object. - * @param getClickThroughRate.index - Index name to target. - * @param getClickThroughRate.startDate - Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getClickThroughRate.endDate - End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * @param getClickThroughRate.index - Index name. + * @param getClickThroughRate.startDate - Start date (`YYYY-MM-DD`) of the period to analyze. + * @param getClickThroughRate.endDate - End date (`YYYY-MM-DD`) of the period to analyze. * @param getClickThroughRate.tags - Filter analytics on the [`analyticsTags`](https://www.algolia.com/doc/api-reference/api-parameters/analyticsTags/) set at search time. Multiple tags can be combined with the operators OR and AND. If a tag contains characters like spaces or parentheses, it must be URL-encoded. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -430,9 +430,9 @@ export function createAnalyticsClient({ * - analytics. * * @param getConversationRate - The getConversationRate object. - * @param getConversationRate.index - Index name to target. - * @param getConversationRate.startDate - Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getConversationRate.endDate - End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * @param getConversationRate.index - Index name. + * @param getConversationRate.startDate - Start date (`YYYY-MM-DD`) of the period to analyze. + * @param getConversationRate.endDate - End date (`YYYY-MM-DD`) of the period to analyze. * @param getConversationRate.tags - Filter analytics on the [`analyticsTags`](https://www.algolia.com/doc/api-reference/api-parameters/analyticsTags/) set at search time. Multiple tags can be combined with the operators OR and AND. If a tag contains characters like spaces or parentheses, it must be URL-encoded. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -483,9 +483,9 @@ export function createAnalyticsClient({ * - analytics. * * @param getNoClickRate - The getNoClickRate object. - * @param getNoClickRate.index - Index name to target. - * @param getNoClickRate.startDate - Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getNoClickRate.endDate - End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * @param getNoClickRate.index - Index name. + * @param getNoClickRate.startDate - Start date (`YYYY-MM-DD`) of the period to analyze. + * @param getNoClickRate.endDate - End date (`YYYY-MM-DD`) of the period to analyze. * @param getNoClickRate.tags - Filter analytics on the [`analyticsTags`](https://www.algolia.com/doc/api-reference/api-parameters/analyticsTags/) set at search time. Multiple tags can be combined with the operators OR and AND. If a tag contains characters like spaces or parentheses, it must be URL-encoded. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -536,9 +536,9 @@ export function createAnalyticsClient({ * - analytics. * * @param getNoResultsRate - The getNoResultsRate object. - * @param getNoResultsRate.index - Index name to target. - * @param getNoResultsRate.startDate - Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getNoResultsRate.endDate - End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * @param getNoResultsRate.index - Index name. + * @param getNoResultsRate.startDate - Start date (`YYYY-MM-DD`) of the period to analyze. + * @param getNoResultsRate.endDate - End date (`YYYY-MM-DD`) of the period to analyze. * @param getNoResultsRate.tags - Filter analytics on the [`analyticsTags`](https://www.algolia.com/doc/api-reference/api-parameters/analyticsTags/) set at search time. Multiple tags can be combined with the operators OR and AND. If a tag contains characters like spaces or parentheses, it must be URL-encoded. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -589,9 +589,9 @@ export function createAnalyticsClient({ * - analytics. * * @param getSearchesCount - The getSearchesCount object. - * @param getSearchesCount.index - Index name to target. - * @param getSearchesCount.startDate - Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getSearchesCount.endDate - End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * @param getSearchesCount.index - Index name. + * @param getSearchesCount.startDate - Start date (`YYYY-MM-DD`) of the period to analyze. + * @param getSearchesCount.endDate - End date (`YYYY-MM-DD`) of the period to analyze. * @param getSearchesCount.tags - Filter analytics on the [`analyticsTags`](https://www.algolia.com/doc/api-reference/api-parameters/analyticsTags/) set at search time. Multiple tags can be combined with the operators OR and AND. If a tag contains characters like spaces or parentheses, it must be URL-encoded. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -642,11 +642,11 @@ export function createAnalyticsClient({ * - analytics. * * @param getSearchesNoClicks - The getSearchesNoClicks object. - * @param getSearchesNoClicks.index - Index name to target. - * @param getSearchesNoClicks.startDate - Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getSearchesNoClicks.endDate - End date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getSearchesNoClicks.limit - Number of records to return (page size). - * @param getSearchesNoClicks.offset - Position of the starting record. Used for paging. 0 is the first record. + * @param getSearchesNoClicks.index - Index name. + * @param getSearchesNoClicks.startDate - Start date (`YYYY-MM-DD`) of the period to analyze. + * @param getSearchesNoClicks.endDate - End date (`YYYY-MM-DD`) of the period to analyze. + * @param getSearchesNoClicks.limit - Number of items to return. + * @param getSearchesNoClicks.offset - Position of the first item to return. * @param getSearchesNoClicks.tags - Filter analytics on the [`analyticsTags`](https://www.algolia.com/doc/api-reference/api-parameters/analyticsTags/) set at search time. Multiple tags can be combined with the operators OR and AND. If a tag contains characters like spaces or parentheses, it must be URL-encoded. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -712,11 +712,11 @@ export function createAnalyticsClient({ * - analytics. * * @param getSearchesNoResults - The getSearchesNoResults object. - * @param getSearchesNoResults.index - Index name to target. - * @param getSearchesNoResults.startDate - Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getSearchesNoResults.endDate - End date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getSearchesNoResults.limit - Number of records to return (page size). - * @param getSearchesNoResults.offset - Position of the starting record. Used for paging. 0 is the first record. + * @param getSearchesNoResults.index - Index name. + * @param getSearchesNoResults.startDate - Start date (`YYYY-MM-DD`) of the period to analyze. + * @param getSearchesNoResults.endDate - End date (`YYYY-MM-DD`) of the period to analyze. + * @param getSearchesNoResults.limit - Number of items to return. + * @param getSearchesNoResults.offset - Position of the first item to return. * @param getSearchesNoResults.tags - Filter analytics on the [`analyticsTags`](https://www.algolia.com/doc/api-reference/api-parameters/analyticsTags/) set at search time. Multiple tags can be combined with the operators OR and AND. If a tag contains characters like spaces or parentheses, it must be URL-encoded. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -782,7 +782,7 @@ export function createAnalyticsClient({ * - analytics. * * @param getStatus - The getStatus object. - * @param getStatus.index - Index name to target. + * @param getStatus.index - Index name. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ getStatus( @@ -820,11 +820,11 @@ export function createAnalyticsClient({ * - analytics. * * @param getTopCountries - The getTopCountries object. - * @param getTopCountries.index - Index name to target. - * @param getTopCountries.startDate - Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getTopCountries.endDate - End date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getTopCountries.limit - Number of records to return (page size). - * @param getTopCountries.offset - Position of the starting record. Used for paging. 0 is the first record. + * @param getTopCountries.index - Index name. + * @param getTopCountries.startDate - Start date (`YYYY-MM-DD`) of the period to analyze. + * @param getTopCountries.endDate - End date (`YYYY-MM-DD`) of the period to analyze. + * @param getTopCountries.limit - Number of items to return. + * @param getTopCountries.offset - Position of the first item to return. * @param getTopCountries.tags - Filter analytics on the [`analyticsTags`](https://www.algolia.com/doc/api-reference/api-parameters/analyticsTags/) set at search time. Multiple tags can be combined with the operators OR and AND. If a tag contains characters like spaces or parentheses, it must be URL-encoded. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -883,12 +883,12 @@ export function createAnalyticsClient({ * - analytics. * * @param getTopFilterAttributes - The getTopFilterAttributes object. - * @param getTopFilterAttributes.index - Index name to target. + * @param getTopFilterAttributes.index - Index name. * @param getTopFilterAttributes.search - User query. - * @param getTopFilterAttributes.startDate - Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getTopFilterAttributes.endDate - End date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getTopFilterAttributes.limit - Number of records to return (page size). - * @param getTopFilterAttributes.offset - Position of the starting record. Used for paging. 0 is the first record. + * @param getTopFilterAttributes.startDate - Start date (`YYYY-MM-DD`) of the period to analyze. + * @param getTopFilterAttributes.endDate - End date (`YYYY-MM-DD`) of the period to analyze. + * @param getTopFilterAttributes.limit - Number of items to return. + * @param getTopFilterAttributes.offset - Position of the first item to return. * @param getTopFilterAttributes.tags - Filter analytics on the [`analyticsTags`](https://www.algolia.com/doc/api-reference/api-parameters/analyticsTags/) set at search time. Multiple tags can be combined with the operators OR and AND. If a tag contains characters like spaces or parentheses, it must be URL-encoded. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -960,12 +960,12 @@ export function createAnalyticsClient({ * * @param getTopFilterForAttribute - The getTopFilterForAttribute object. * @param getTopFilterForAttribute.attribute - Attribute name. - * @param getTopFilterForAttribute.index - Index name to target. + * @param getTopFilterForAttribute.index - Index name. * @param getTopFilterForAttribute.search - User query. - * @param getTopFilterForAttribute.startDate - Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getTopFilterForAttribute.endDate - End date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getTopFilterForAttribute.limit - Number of records to return (page size). - * @param getTopFilterForAttribute.offset - Position of the starting record. Used for paging. 0 is the first record. + * @param getTopFilterForAttribute.startDate - Start date (`YYYY-MM-DD`) of the period to analyze. + * @param getTopFilterForAttribute.endDate - End date (`YYYY-MM-DD`) of the period to analyze. + * @param getTopFilterForAttribute.limit - Number of items to return. + * @param getTopFilterForAttribute.offset - Position of the first item to return. * @param getTopFilterForAttribute.tags - Filter analytics on the [`analyticsTags`](https://www.algolia.com/doc/api-reference/api-parameters/analyticsTags/) set at search time. Multiple tags can be combined with the operators OR and AND. If a tag contains characters like spaces or parentheses, it must be URL-encoded. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -1046,12 +1046,12 @@ export function createAnalyticsClient({ * - analytics. * * @param getTopFiltersNoResults - The getTopFiltersNoResults object. - * @param getTopFiltersNoResults.index - Index name to target. + * @param getTopFiltersNoResults.index - Index name. * @param getTopFiltersNoResults.search - User query. - * @param getTopFiltersNoResults.startDate - Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getTopFiltersNoResults.endDate - End date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getTopFiltersNoResults.limit - Number of records to return (page size). - * @param getTopFiltersNoResults.offset - Position of the starting record. Used for paging. 0 is the first record. + * @param getTopFiltersNoResults.startDate - Start date (`YYYY-MM-DD`) of the period to analyze. + * @param getTopFiltersNoResults.endDate - End date (`YYYY-MM-DD`) of the period to analyze. + * @param getTopFiltersNoResults.limit - Number of items to return. + * @param getTopFiltersNoResults.offset - Position of the first item to return. * @param getTopFiltersNoResults.tags - Filter analytics on the [`analyticsTags`](https://www.algolia.com/doc/api-reference/api-parameters/analyticsTags/) set at search time. Multiple tags can be combined with the operators OR and AND. If a tag contains characters like spaces or parentheses, it must be URL-encoded. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -1122,13 +1122,13 @@ export function createAnalyticsClient({ * - analytics. * * @param getTopHits - The getTopHits object. - * @param getTopHits.index - Index name to target. + * @param getTopHits.index - Index name. * @param getTopHits.search - User query. * @param getTopHits.clickAnalytics - Whether to include [click and conversion](https://www.algolia.com/doc/guides/sending-events/getting-started/) rates for a search. - * @param getTopHits.startDate - Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getTopHits.endDate - End date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getTopHits.limit - Number of records to return (page size). - * @param getTopHits.offset - Position of the starting record. Used for paging. 0 is the first record. + * @param getTopHits.startDate - Start date (`YYYY-MM-DD`) of the period to analyze. + * @param getTopHits.endDate - End date (`YYYY-MM-DD`) of the period to analyze. + * @param getTopHits.limit - Number of items to return. + * @param getTopHits.offset - Position of the first item to return. * @param getTopHits.tags - Filter analytics on the [`analyticsTags`](https://www.algolia.com/doc/api-reference/api-parameters/analyticsTags/) set at search time. Multiple tags can be combined with the operators OR and AND. If a tag contains characters like spaces or parentheses, it must be URL-encoded. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -1204,14 +1204,14 @@ export function createAnalyticsClient({ * - analytics. * * @param getTopSearches - The getTopSearches object. - * @param getTopSearches.index - Index name to target. + * @param getTopSearches.index - Index name. * @param getTopSearches.clickAnalytics - Whether to include [click and conversion](https://www.algolia.com/doc/guides/sending-events/getting-started/) rates for a search. - * @param getTopSearches.startDate - Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getTopSearches.endDate - End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * @param getTopSearches.startDate - Start date (`YYYY-MM-DD`) of the period to analyze. + * @param getTopSearches.endDate - End date (`YYYY-MM-DD`) of the period to analyze. * @param getTopSearches.orderBy - Reorder the results. * @param getTopSearches.direction - Sorting direction of the results: ascending or descending. - * @param getTopSearches.limit - Number of records to return (page size). - * @param getTopSearches.offset - Position of the starting record. Used for paging. 0 is the first record. + * @param getTopSearches.limit - Number of items to return. + * @param getTopSearches.offset - Position of the first item to return. * @param getTopSearches.tags - Filter analytics on the [`analyticsTags`](https://www.algolia.com/doc/api-reference/api-parameters/analyticsTags/) set at search time. Multiple tags can be combined with the operators OR and AND. If a tag contains characters like spaces or parentheses, it must be URL-encoded. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -1292,9 +1292,9 @@ export function createAnalyticsClient({ * - analytics. * * @param getUsersCount - The getUsersCount object. - * @param getUsersCount.index - Index name to target. - * @param getUsersCount.startDate - Start date (a string in the format `YYYY-MM-DD`) of the period to analyze. - * @param getUsersCount.endDate - End date (a string in the format `YYYY-MM-DD`) of the period to analyze. + * @param getUsersCount.index - Index name. + * @param getUsersCount.startDate - Start date (`YYYY-MM-DD`) of the period to analyze. + * @param getUsersCount.endDate - End date (`YYYY-MM-DD`) of the period to analyze. * @param getUsersCount.tags - Filter analytics on the [`analyticsTags`](https://www.algolia.com/doc/api-reference/api-parameters/analyticsTags/) set at search time. Multiple tags can be combined with the operators OR and AND. If a tag contains characters like spaces or parentheses, it must be URL-encoded. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ diff --git a/packages/client-search/model/acl.ts b/packages/client-search/model/acl.ts index c3522561e..d7413dac1 100644 --- a/packages/client-search/model/acl.ts +++ b/packages/client-search/model/acl.ts @@ -1,7 +1,7 @@ // 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. /** - * API key permissions: `addObject`: required to add or update records, copy or move an index. `analytics`: required to access the Analytics API. `browse`: required to view records `deleteIndex`: required to delete indices. `deleteObject`: required to delete records. `editSettings`: required to change index settings. `inference`: required to access the Inference API. `listIndexes`: required to list indices. `logs`: required to access logs of search and indexing operations. `recommendation`: required to access the Personalization and Recommend APIs. `search`: required to search records `seeUnretrievableAttributes`: required to retrieve [`unretrievableAttributes`](https://www.algolia.com/doc/api-reference/api-parameters/unretrievableAttributes/) for all operations that return records. `settings`: required to examine index settings. + * Access control list permissions. */ export type Acl = | 'addObject' diff --git a/packages/client-search/model/action.ts b/packages/client-search/model/action.ts index 339db6126..dd3583e54 100644 --- a/packages/client-search/model/action.ts +++ b/packages/client-search/model/action.ts @@ -1,7 +1,7 @@ // 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. /** - * Type of batch operation. + * Type of indexing operation. */ export type Action = | 'addObject' diff --git a/packages/client-search/model/addApiKeyResponse.ts b/packages/client-search/model/addApiKeyResponse.ts index 3817c9691..9f57140d0 100644 --- a/packages/client-search/model/addApiKeyResponse.ts +++ b/packages/client-search/model/addApiKeyResponse.ts @@ -7,7 +7,7 @@ export type AddApiKeyResponse = { key: string; /** - * Timestamp of creation in [ISO-8601](https://wikipedia.org/wiki/ISO_8601) format. + * Timestamp of creation in [ISO 8601](https://wikipedia.org/wiki/ISO_8601) format. */ createdAt: string; }; diff --git a/packages/client-search/model/anchoring.ts b/packages/client-search/model/anchoring.ts index c77a11939..cb727242e 100644 --- a/packages/client-search/model/anchoring.ts +++ b/packages/client-search/model/anchoring.ts @@ -1,6 +1,6 @@ // 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. /** - * Whether the pattern parameter matches the beginning (`startsWith`) or end (`endsWith`) of the query string, is an exact match (`is`), or a partial match (`contains`). + * Which part of the search query the pattern should match: - `startsWith`. The pattern must match the begginning of the query. - `endsWith`. The pattern must match the end of the query. - `is`. The pattern must match the query exactly. - `contains`. The pattern must match anywhere in the query. Empty queries are only allowed as pattern with `anchoring: is`. */ export type Anchoring = 'contains' | 'endsWith' | 'is' | 'startsWith'; diff --git a/packages/client-search/model/apiKey.ts b/packages/client-search/model/apiKey.ts index f30f69756..665d39c57 100644 --- a/packages/client-search/model/apiKey.ts +++ b/packages/client-search/model/apiKey.ts @@ -7,42 +7,42 @@ import type { Acl } from './acl'; */ export type ApiKey = { /** - * [Permissions](https://www.algolia.com/doc/guides/security/api-keys/#access-control-list-acl) associated with the key. + * Permissions that determine the type of API requests this key can make. The required ACL is listed in each endpoint\'s reference. For more information, see [access control list](https://www.algolia.com/doc/guides/security/api-keys/#access-control-list-acl). */ acl: Acl[]; /** - * Description of an API key for you and your team members. + * Description of an API key to help you identify this API key. */ description?: string; /** - * Restricts this API key to a list of indices or index patterns. If the list is empty, all indices are allowed. Specify either an exact index name or a pattern with a leading or trailing wildcard character (or both). For example: - `dev_*` matches all indices starting with \"dev_\" - `*_dev` matches all indices ending with \"_dev\" - `*_products_*` matches all indices containing \"_products_\". + * Index names or patterns that this API key can access. By default, an API key can access all indices in the same application. You can use leading and trailing wildcard characters (`*`): - `dev_*` matches all indices starting with \"dev_\". - `*_dev` matches all indices ending with \"_dev\". - `*_products_*` matches all indices containing \"_products_\". */ indexes?: string[]; /** - * Maximum number of hits this API key can retrieve in one query. If zero, no limit is enforced. > **Note**: Use this parameter to protect you from third-party attempts to retrieve your entire content by massively querying the index. + * Maximum number of results this API key can retrieve in one query. By default, there\'s no limit. */ maxHitsPerQuery?: number; /** - * Maximum number of API calls per hour allowed from a given IP address or [user token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken/). Each time an API call is performed with this key, a check is performed. If there were more than the specified number of calls within the last hour, the API returns an error with the status code `429` (Too Many Requests). > **Note**: Use this parameter to protect you from third-party attempts to retrieve your entire content by massively querying the index. + * Maximum number of API requests allowed per IP address or [user token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken/) per hour. If this limit is reached, the API returns an error with status code `429`. By default, there\'s no limit. */ maxQueriesPerIPPerHour?: number; /** - * Force some [query parameters](https://www.algolia.com/doc/api-reference/api-parameters/) to be applied for each query made with this API key. It\'s a URL-encoded query string. + * Query parameters to add when making API requests with this API key. To restrict this API key to specific IP addresses, add the `restrictSources` parameter. You can only add a single source, but you can provide a range of IP addresses. Creating an API key fails if the request is made from an IP address that\'s outside the restricted range. */ queryParameters?: string; /** - * Restrict this API key to specific [referrers](https://www.algolia.com/doc/guides/security/api-keys/in-depth/api-key-restrictions/#http-referrers). If empty, all referrers are allowed. For example: - `https://algolia.com/_*` matches all referrers starting with \"https://algolia.com/\" - `*.algolia.com` matches all referrers ending with \".algolia.com\" - `*algolia.com*` allows everything in the domain \"algolia.com\". + * Allowed HTTP referrers for this API key. By default, all referrers are allowed. You can use leading and trailing wildcard characters (`*`): - `https://algolia.com/_*` allows all referrers starting with \"https://algolia.com/\" - `*.algolia.com` allows all referrers ending with \".algolia.com\" - `*algolia.com*` allows all referrers in the domain \"algolia.com\". Like all HTTP headers, referrers can be spoofed. Don\'t rely on them to secure your data. For more information, see [HTTP referrer restrictions](https://www.algolia.com/doc/guides/security/security-best-practices/#http-referrers-restrictions). */ referers?: string[]; /** - * Validity duration of a key (in seconds). The key will automatically be removed after this time has expired. The default value of 0 never expires. Short-lived API keys are useful to grant temporary access to your data. For example, in mobile apps, you can\'t [control when users update your app](https://www.algolia.com/doc/guides/security/security-best-practices/#use-secured-api-keys-in-mobile-apps). So instead of encoding keys into your app as you would for a web app, you should dynamically fetch them from your mobile app\'s backend. + * Duration (in seconds) after which the API key expires. By default, API keys don\'t expire. */ validity?: number; }; diff --git a/packages/client-search/model/aroundPrecision.ts b/packages/client-search/model/aroundPrecision.ts index 71120c73e..937a1e87e 100644 --- a/packages/client-search/model/aroundPrecision.ts +++ b/packages/client-search/model/aroundPrecision.ts @@ -3,6 +3,6 @@ import type { AroundPrecisionFromValueInner } from './aroundPrecisionFromValueInner'; /** - * Precision of a geographical search (in meters), to [group results that are more or less the same distance from a central point](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/in-depth/geo-ranking-precision/). + * Precision of a coordinate-based search in meters to group results with similar distances. The Geo ranking criterion considers all matches within the same range of distances to be equal. */ export type AroundPrecision = AroundPrecisionFromValueInner[] | number; diff --git a/packages/client-search/model/aroundPrecisionFromValueInner.ts b/packages/client-search/model/aroundPrecisionFromValueInner.ts index 14a0e3bb7..c3850a800 100644 --- a/packages/client-search/model/aroundPrecisionFromValueInner.ts +++ b/packages/client-search/model/aroundPrecisionFromValueInner.ts @@ -1,7 +1,16 @@ // 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. +/** + * Range object with lower and upper values in meters to define custom ranges. + */ export type AroundPrecisionFromValueInner = { + /** + * Lower boundary of a range in meters. The Geo ranking criterion considers all records within the range to be equal. + */ from?: number; + /** + * Upper boundary of a range in meters. The Geo ranking criterion considers all records within the range to be equal. + */ value?: number; }; diff --git a/packages/client-search/model/aroundRadius.ts b/packages/client-search/model/aroundRadius.ts index 6c99817b2..1c4ae8df2 100644 --- a/packages/client-search/model/aroundRadius.ts +++ b/packages/client-search/model/aroundRadius.ts @@ -3,6 +3,6 @@ import type { AroundRadiusAll } from './aroundRadiusAll'; /** - * [Maximum radius](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#increase-the-search-radius) for a geographical search (in meters). + * Maximum radius for a search around a central location. This parameter works in combination with the `aroundLatLng` and `aroundLatLngViaIP` parameters. By default, the search radius is determined automatically from the density of hits around the central location. The search radius is small if there are many hits close to the central coordinates. */ export type AroundRadius = AroundRadiusAll | number; diff --git a/packages/client-search/model/aroundRadiusAll.ts b/packages/client-search/model/aroundRadiusAll.ts index 1dd22ed57..e5f107060 100644 --- a/packages/client-search/model/aroundRadiusAll.ts +++ b/packages/client-search/model/aroundRadiusAll.ts @@ -1,3 +1,6 @@ // 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. +/** + * Return all records with a valid `_geoloc` attribute. Don\'t filter by distance. + */ export type AroundRadiusAll = 'all'; diff --git a/packages/client-search/model/automaticFacetFilter.ts b/packages/client-search/model/automaticFacetFilter.ts index 98a2e1e7a..ca83695bf 100644 --- a/packages/client-search/model/automaticFacetFilter.ts +++ b/packages/client-search/model/automaticFacetFilter.ts @@ -1,21 +1,21 @@ // 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. /** - * Automatic facet Filter. + * Filter or optional filter to be applied to the search. */ export type AutomaticFacetFilter = { /** - * Attribute to filter on. This must match a facet placeholder in the Rule\'s pattern. + * Facet name to be applied as filter. The name must match placeholders in the `pattern` parameter. For example, with `pattern: {facet:genre}`, `automaticFacetFilters` must be `genre`. */ facet: string; /** - * Score for the filter. Typically used for optional or disjunctive filters. + * Filter scores to give different weights to individual filters. */ score?: number; /** - * Whether the filter is disjunctive (true) or conjunctive (false). + * Whether the filter is disjunctive or conjunctive. If true the filter has multiple matches, multiple occurences are combined with the logical `OR` operation. If false, multiple occurences are combined with the logical `AND` operation. */ disjunctive?: boolean; }; diff --git a/packages/client-search/model/automaticFacetFilters.ts b/packages/client-search/model/automaticFacetFilters.ts index 0ac46a30f..725561f8d 100644 --- a/packages/client-search/model/automaticFacetFilters.ts +++ b/packages/client-search/model/automaticFacetFilters.ts @@ -3,6 +3,6 @@ import type { AutomaticFacetFilter } from './automaticFacetFilter'; /** - * Names of facets to which automatic filtering must be applied; they must match the facet name of a facet value placeholder in the query pattern. + * Filter to be applied to the search. You can use this to respond to search queries that match a facet value. For example, if users search for \"comedy\", which matches a facet value of the \"genre\" facet, you can filter the results to show the top-ranked comedy movies. */ export type AutomaticFacetFilters = AutomaticFacetFilter[] | string[]; diff --git a/packages/client-search/model/baseIndexSettings.ts b/packages/client-search/model/baseIndexSettings.ts index 3d026541d..a35d8cbd3 100644 --- a/packages/client-search/model/baseIndexSettings.ts +++ b/packages/client-search/model/baseIndexSettings.ts @@ -2,82 +2,87 @@ export type BaseIndexSettings = { /** - * Creates [replicas](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/replicas/), which are copies of a primary index with the same records but different settings. + * Attributes used for [faceting](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/). Facets are ways to categorize search results based on attributes. Facets can be used to let user filter search results. By default, no attribute is used for faceting. **Modifiers**
filterOnly(\"ATTRIBUTE\")
Allows using this attribute as a filter, but doesn\'t evalue the facet values.
searchable(\"ATTRIBUTE\")
Allows searching for facet values.
afterDistinct(\"ATTRIBUTE\")
Evaluates the facet count _after_ deduplication with `distinct`. This ensures accurate facet counts. You can apply this modifier to searchable facets: `afterDistinct(searchable(ATTRIBUTE))`.
Without modifiers, the attribute is used as a regular facet. + */ + attributesForFaceting?: string[]; + + /** + * Creates [replica indices](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/replicas/). Replicas are copies of a primary index with the same records but different settings, synonyms, or rules. If you want to offer a different ranking or sorting of your search results, you\'ll use replica indices. All index operations on a primary index are automatically forwarded to its replicas. To add a replica index, you must provide the complete set of replicas to this parameter. If you omit a replica from this list, the replica turns into a regular, standalone index that will no longer by synced with the primary index. **Modifier**
virtual(\"REPLICA\")
Create a virtual replica, Virtual replicas don\'t increase the number of records and are optimized for [Relevant sorting](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/relevant-sort/).
Without modifier, a standard replica is created, which duplicates your record count and is used for strict, or [exhaustive sorting](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/exhaustive-sort/). */ replicas?: string[]; /** - * Maximum number of hits accessible through pagination. + * Maximum number of search results that can be obtained through pagination. Higher pagination limits might slow down your search. For pagination limits above 1,000, the sorting of results beyond the 1,000th hit can\'t be guaranteed. */ paginationLimitedTo?: number; /** - * Attributes that can\'t be retrieved at query time. + * Attributes that can\'t be retrieved at query time. This can be useful if you want to use an attribute for ranking or to [restrict access](https://www.algolia.com/doc/guides/security/api-keys/how-to/user-restricted-access-to-data/), but don\'t want to include it in the search results. */ unretrievableAttributes?: string[]; /** - * Words for which you want to turn off [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/). + * 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. */ disableTypoToleranceOnWords?: string[]; /** - * Attributes in your index to which [Japanese transliteration](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/#japanese-transliteration-and-type-ahead) applies. This will ensure that words indexed in Katakana or Kanji can also be searched in Hiragana. + * Attributes, for which you want to support [Japanese transliteration](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/#japanese-transliteration-and-type-ahead). Transliteration supports searching in any of the Japanese writing systems. To support transliteration, you must set the indexing language to Japanese. */ attributesToTransliterate?: string[]; /** - * Attributes on which to split [camel case](https://wikipedia.org/wiki/Camel_case) words. + * Attributes for which to split [camel case](https://wikipedia.org/wiki/Camel_case) words. */ camelCaseAttributes?: string[]; /** - * Attributes in your index to which [word segmentation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/how-to/customize-segmentation/) (decompounding) applies. + * Searchable attributes to which Algolia should apply [word segmentation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/how-to/customize-segmentation/) (decompounding). Compound words are formed by combining two or more individual words, and are particularly prevalent in Germanic languages—for example, \"firefighter\". With decompounding, the individual components are indexed separately. You can specify different lists for different languages. Decompounding is supported for these languages: Dutch (`nl`), German (`de`), Finnish (`fi`), Danish (`da`), Swedish (`sv`), and Norwegian (`no`). */ decompoundedAttributes?: Record; /** - * Set the languages of your index, for language-specific processing steps such as [tokenization](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/tokenization/) and [normalization](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/normalization/). + * [ISO code](https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes) for a language for language-specific processing steps, such as word detection and dictionary settings. **You should always specify an indexing 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/). */ indexLanguages?: string[]; /** - * Attributes for which you want to turn off [prefix matching](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/#adjusting-prefix-search). + * Searchable attributes for which you want to turn off [prefix matching](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/#adjusting-prefix-search). */ disablePrefixOnAttributes?: string[]; /** - * Incidates whether the engine compresses arrays with exclusively non-negative integers. When enabled, the compressed arrays may be reordered. + * Whether arrays with exclusively non-negative integers should be compressed for better performance. If true, the compressed arrays may be reordered. */ allowCompressionOfIntegerArray?: boolean; /** - * Numeric attributes that can be used as [numerical filters](https://www.algolia.com/doc/guides/managing-results/rules/detecting-intent/how-to/applying-a-custom-filter-for-a-specific-query/#numerical-filters). + * Numeric attributes that can be used as [numerical filters](https://www.algolia.com/doc/guides/managing-results/rules/detecting-intent/how-to/applying-a-custom-filter-for-a-specific-query/#numerical-filters). By default, all numeric attributes are available as numerical filters. For faster indexing, reduce the number of numeric attributes. If you want to turn off filtering for all numeric attributes, specifiy an attribute that doesn\'t exist in your index, such as `NO_NUMERIC_FILTERING`. **Modifier**
equalOnly(\"ATTRIBUTE\")
Support only filtering based on equality comparisons `=` and `!=`.
Without modifier, all numeric comparisons are supported. */ numericAttributesForFiltering?: string[]; /** - * Controls which separators are added to an Algolia index as part of [normalization](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/#what-does-normalization-mean). Separators are all non-letter characters except spaces and currency characters, such as $€£¥. + * 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. */ separatorsToIndex?: string; /** - * [Attributes used for searching](https://www.algolia.com/doc/guides/managing-results/must-do/searchable-attributes/), including determining [if matches at the beginning of a word are important (ordered) or not (unordered)](https://www.algolia.com/doc/guides/managing-results/must-do/searchable-attributes/how-to/configuring-searchable-attributes-the-right-way/#understanding-word-position). + * Attributes used for searching. By default, all attributes are searchable and the [Attribute](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#attribute) ranking criterion is turned off. With a non-empty list, Algolia only returns results with matches in the selected attributes. In addition, the Attribute ranking criterion is turned on: matches in attributes that are higher in the list of `searchableAttributes` rank first. To make matches in two attributes rank equally, include them in a comma-separated string, such as `\"title,alternate_title\"`. Attributes with the same priority are always unordered. For more information, see [Searchable attributes](https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/how-to/setting-searchable-attributes/). **Modifier**
unordered(\"ATTRIBUTE\")
Ignore the position of a match within the attribute.
Without modifier, matches at the beginning of an attribute rank higer than matches at the end. */ searchableAttributes?: string[]; /** - * Lets you store custom data in your indices. + * An object with custom data. You can store up to 32 kB as custom data. */ userData?: any | null; /** - * A list of characters and their normalized replacements to override Algolia\'s default [normalization](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/normalization/). + * Characters and their normalized replacements. This overrides Algolia\'s default [normalization](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/normalization/). */ customNormalization?: Record>; /** - * Name of the deduplication attribute to be used with Algolia\'s [_distinct_ feature](https://www.algolia.com/doc/guides/managing-results/refine-results/grouping/#introducing-algolias-distinct-feature). + * Attribute that should be used to establish groups of results. All records with the same value for this attribute are considered a group. You can combine `attributeForDistinct` with the `distinct` search parameter to control how many items per group are included in the search results. If you want to use the same attribute also for faceting, use the `afterDistinct` modifier of the `attributesForFaceting` setting. This applies faceting _after_ deduplication, which will result in accurate facet counts. */ attributeForDistinct?: string; }; diff --git a/packages/client-search/model/baseSearchParamsWithoutQuery.ts b/packages/client-search/model/baseSearchParamsWithoutQuery.ts index 33825f13f..95ae5b039 100644 --- a/packages/client-search/model/baseSearchParamsWithoutQuery.ts +++ b/packages/client-search/model/baseSearchParamsWithoutQuery.ts @@ -9,12 +9,12 @@ import type { TagFilters } from './tagFilters'; export type BaseSearchParamsWithoutQuery = { /** - * Overrides the query parameter and performs a more generic search. + * 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](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering/) the query with numeric, facet, or tag filters. + * Filter the search so that only records with matching values are included in the results. These filters are supported: - **Numeric filters.** ` `, where `` is one of `<`, `<=`, `=`, `!=`, `>`, `>=`. - **Ranges.** `: TO ` where `` and `` are the lower and upper limits of the range (inclusive). - **Facet filters.** `:` where `` is a facet attribute (case-sensitive) and `` a facet value. - **Tag filters.** `_tags:` or just `` (case-sensitive). - **Boolean filters.** `: 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; @@ -27,47 +27,47 @@ export type BaseSearchParamsWithoutQuery = { tagFilters?: TagFilters; /** - * Determines how to calculate [filter scores](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering/in-depth/filter-scoring/#accumulating-scores-with-sumorfiltersscores). If `false`, maximum score is kept. If `true`, score is summed. + * 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 query to only look at a subset of your [searchable attributes](https://www.algolia.com/doc/guides/managing-results/must-do/searchable-attributes/). + * Restricts a search to a subset of your searchable attributes. */ restrictSearchableAttributes?: string[]; /** - * Returns [facets](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#contextual-facet-values-and-counts), their facet values, and the number of matching facet values. + * 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?: string[]; /** - * Forces faceting to be applied after [de-duplication](https://www.algolia.com/doc/guides/managing-results/refine-results/grouping/) (with the distinct feature). Alternatively, the `afterDistinct` [modifier](https://www.algolia.com/doc/api-reference/api-parameters/attributesForFaceting/#modifiers) of `attributesForFaceting` allows for more granular control. + * 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; /** - * Page to retrieve (the first page is `0`, not `1`). + * Page of search results to retrieve. */ page?: number; /** - * Specifies the offset of the first hit to return. > **Note**: Using `page` and `hitsPerPage` is the recommended method for [paging results](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/). However, you can use `offset` and `length` to implement [an alternative approach to paging](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/#retrieving-a-subset-of-records-with-offset-and-length). + * Position of the first hit to retrieve. */ offset?: number; /** - * Sets the number of hits to retrieve (for use with `offset`). > **Note**: Using `page` and `hitsPerPage` is the recommended method for [paging results](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/). However, you can use `offset` and `length` to implement [an alternative approach to paging](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/#retrieving-a-subset-of-records-with-offset-and-length). + * Number of hits to retrieve (used in combination with `offset`). */ length?: number; /** - * Search for entries [around a central location](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filter-around-a-central-point), enabling a geographical search within a circular area. + * Coordinates for the center of a circle, expressed as a comma-separated string of latitude and longitude. Only records included within 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; /** - * Search for entries around a location. The location is automatically computed from the requester\'s IP address. + * Whether to obtain the coordinates from the request\'s IP address. */ aroundLatLngViaIP?: boolean; @@ -76,62 +76,57 @@ export type BaseSearchParamsWithoutQuery = { aroundPrecision?: AroundPrecision; /** - * Minimum radius (in meters) used for a geographical search when `aroundRadius` isn\'t set. + * Minimum radius (in meters) for a search around a location when `aroundRadius` isn\'t set. */ minimumAroundRadius?: number; /** - * Search inside a [rectangular area](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas) (in geographical coordinates). + * 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?: number[][]; /** - * Search inside a [polygon](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas) (in geographical coordinates). + * 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?: number[][]; /** - * Changes the default values of parameters that work best for a natural language query, such as `ignorePlurals`, `removeStopWords`, `removeWordsIfNoResults`, `analyticsTags`, and `ruleContexts`. These parameters work well together when the query consists of fuller natural language strings instead of keywords, for example when processing voice search queries. + * 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?: string[]; /** - * Assigns [rule contexts](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/how-to/customize-search-results-by-platform/#whats-a-context) to search queries. + * 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?: string[]; /** - * Defines how much [Personalization affects results](https://www.algolia.com/doc/guides/personalization/personalizing-results/in-depth/configuring-personalization/#understanding-personalization-impact). + * 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; /** - * Associates a [user token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken/) with the current search. + * 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; /** - * Incidates whether the search response includes [detailed ranking information](https://www.algolia.com/doc/guides/building-search-ui/going-further/backend-search/in-depth/understanding-the-api-response/#ranking-information). + * Whether the search response should include detailed ranking information. */ getRankingInfo?: boolean; /** - * Enriches the API\'s response with information about how the query was processed. - */ - explain?: string[]; - - /** - * Whether to take into account an index\'s synonyms for a particular search. + * Whether to take into account an index\'s synonyms for this search. */ synonyms?: boolean; /** - * Indicates whether a query ID parameter is included in the search response. This is required for [tracking click and conversion events](https://www.algolia.com/doc/guides/sending-events/concepts/event-types/#events-related-to-algolia-requests). + * 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; /** - * Indicates whether this query will be included in [analytics](https://www.algolia.com/doc/guides/search-analytics/guides/exclude-queries/). + * Whether this search will be included in Analytics. */ analytics?: boolean; @@ -141,12 +136,12 @@ export type BaseSearchParamsWithoutQuery = { analyticsTags?: string[]; /** - * Whether to include or exclude a query from the processing-time percentile computation. + * Whether to include this search when calculating processing-time percentiles. */ percentileComputation?: boolean; /** - * Incidates whether this search will be considered in A/B testing. + * Whether to enable A/B testing for this search. */ enableABTest?: boolean; }; diff --git a/packages/client-search/model/baseSearchResponse.ts b/packages/client-search/model/baseSearchResponse.ts index abd29c39d..6d3dd06f9 100644 --- a/packages/client-search/model/baseSearchResponse.ts +++ b/packages/client-search/model/baseSearchResponse.ts @@ -22,7 +22,7 @@ export type BaseSearchResponse = Record & { aroundLatLng?: string; /** - * Automatically-computed radius. + * Distance from a central coordinate provided by `aroundLatLng`. */ automaticRadius?: string; @@ -44,7 +44,7 @@ export type BaseSearchResponse = Record & { exhaustiveTypo?: boolean; /** - * Mapping of each facet name to the corresponding facet counts. + * Facet counts. */ facets?: Record>; @@ -74,12 +74,12 @@ export type BaseSearchResponse = Record & { message?: string; /** - * Number of hits the search query matched. + * Number of results (hits). */ nbHits: number; /** - * Number of pages of results for the current query. + * Number of pages of results. */ nbPages: number; @@ -89,7 +89,7 @@ export type BaseSearchResponse = Record & { nbSortedHits?: number; /** - * Page to retrieve (the first page is `0`, not `1`). + * Page of search results to retrieve. */ page: number; @@ -128,7 +128,7 @@ export type BaseSearchResponse = Record & { serverUsed?: string; /** - * Lets you store custom data in your indices. + * An object with custom data. You can store up to 32 kB as custom data. */ userData?: any | null; diff --git a/packages/client-search/model/batchDictionaryEntriesParams.ts b/packages/client-search/model/batchDictionaryEntriesParams.ts index fe96c3480..1016e4797 100644 --- a/packages/client-search/model/batchDictionaryEntriesParams.ts +++ b/packages/client-search/model/batchDictionaryEntriesParams.ts @@ -3,16 +3,16 @@ import type { BatchDictionaryEntriesRequest } from './batchDictionaryEntriesRequest'; /** - * `batchDictionaryEntries` parameters. + * Request body for updating dictionary entries. */ export type BatchDictionaryEntriesParams = { /** - * Incidates whether to replace all custom entries in the dictionary with the ones sent with this request. + * Whether to replace all custom entries in the dictionary with the ones sent with this request. */ clearExistingDictionaryEntries?: boolean; /** - * Operations to batch. + * List of additions and deletions to your dictionaries. */ requests: BatchDictionaryEntriesRequest[]; }; diff --git a/packages/client-search/model/batchResponse.ts b/packages/client-search/model/batchResponse.ts index 500715628..b67702490 100644 --- a/packages/client-search/model/batchResponse.ts +++ b/packages/client-search/model/batchResponse.ts @@ -2,12 +2,12 @@ export type BatchResponse = { /** - * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the `task` operation and this `taskID`. + * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the [`task` operation](#tag/Indices/operation/getTask) and this `taskID`. */ taskID: number; /** - * Unique object (record) identifiers. + * Unique record identifiers. */ objectIDs: string[]; }; diff --git a/packages/client-search/model/builtInOperation.ts b/packages/client-search/model/builtInOperation.ts index 8bcf7b094..d3df17410 100644 --- a/packages/client-search/model/builtInOperation.ts +++ b/packages/client-search/model/builtInOperation.ts @@ -3,13 +3,13 @@ import type { BuiltInOperationType } from './builtInOperationType'; /** - * To update an attribute without pushing the entire record, you can use these built-in operations. + * Update to perform on the attribute. */ export type BuiltInOperation = { _operation: BuiltInOperationType; /** - * Value that corresponds to the operation, for example an `Increment` or `Decrement` step, `Add` or `Remove` value. + * Value that corresponds to the operation, for example an `Increment` or `Decrement` step, or an `Add` or `Remove` value. */ value: string; }; diff --git a/packages/client-search/model/builtInOperationType.ts b/packages/client-search/model/builtInOperationType.ts index 71a7cd154..56d0ed532 100644 --- a/packages/client-search/model/builtInOperationType.ts +++ b/packages/client-search/model/builtInOperationType.ts @@ -1,7 +1,7 @@ // 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. /** - * Operation to apply to the attribute. + * How to change the attribute. */ export type BuiltInOperationType = | 'Add' diff --git a/packages/client-search/model/clientMethodProps.ts b/packages/client-search/model/clientMethodProps.ts index 086014ede..400d98c45 100644 --- a/packages/client-search/model/clientMethodProps.ts +++ b/packages/client-search/model/clientMethodProps.ts @@ -36,15 +36,15 @@ import type { UpdatedAtResponse } from './updatedAtResponse'; */ export type AddOrUpdateObjectProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** - * Unique record (object) identifier. + * Unique record identifier. */ objectID: string; /** - * Algolia record. + * The record, a schemaless object with attributes that are useful in the context of search and discovery. */ body: Record; }; @@ -54,7 +54,7 @@ export type AddOrUpdateObjectProps = { */ export type AssignUserIdProps = { /** - * UserID to assign. + * User ID to assign. */ xAlgoliaUserID: string; assignUserIdParams: AssignUserIdParams; @@ -65,7 +65,7 @@ export type AssignUserIdProps = { */ export type BatchProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; batchWriteParams: BatchWriteParams; @@ -76,7 +76,7 @@ export type BatchProps = { */ export type BatchAssignUserIdsProps = { /** - * UserID to assign. + * User ID to assign. */ xAlgoliaUserID: string; batchAssignUserIdsParams: BatchAssignUserIdsParams; @@ -87,7 +87,7 @@ export type BatchAssignUserIdsProps = { */ export type BatchDictionaryEntriesProps = { /** - * Dictionary to search in. + * Dictionary type in which to search. */ dictionaryName: DictionaryType; batchDictionaryEntriesParams: BatchDictionaryEntriesParams; @@ -98,7 +98,7 @@ export type BatchDictionaryEntriesProps = { */ export type BrowseProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; browseParams?: BrowseParams; @@ -109,7 +109,7 @@ export type BrowseProps = { */ export type ClearObjectsProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; }; @@ -119,11 +119,11 @@ export type ClearObjectsProps = { */ export type ClearRulesProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** - * Indicates whether changed index settings are forwarded to the replica indices. + * Whether changes are applied to replica indices. */ forwardToReplicas?: boolean; }; @@ -133,11 +133,11 @@ export type ClearRulesProps = { */ export type ClearSynonymsProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** - * Indicates whether changed index settings are forwarded to the replica indices. + * Whether changes are applied to replica indices. */ forwardToReplicas?: boolean; }; @@ -221,7 +221,7 @@ export type DeleteApiKeyProps = { */ export type DeleteByProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; deleteByParams: DeleteByParams; @@ -232,7 +232,7 @@ export type DeleteByProps = { */ export type DeleteIndexProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; }; @@ -242,11 +242,11 @@ export type DeleteIndexProps = { */ export type DeleteObjectProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** - * Unique record (object) identifier. + * Unique record identifier. */ objectID: string; }; @@ -256,7 +256,7 @@ export type DeleteObjectProps = { */ export type DeleteRuleProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** @@ -264,7 +264,7 @@ export type DeleteRuleProps = { */ objectID: string; /** - * Indicates whether changed index settings are forwarded to the replica indices. + * Whether changes are applied to replica indices. */ forwardToReplicas?: boolean; }; @@ -284,7 +284,7 @@ export type DeleteSourceProps = { */ export type DeleteSynonymProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** @@ -292,7 +292,7 @@ export type DeleteSynonymProps = { */ objectID: string; /** - * Indicates whether changed index settings are forwarded to the replica indices. + * Whether changes are applied to replica indices. */ forwardToReplicas?: boolean; }; @@ -312,7 +312,7 @@ export type GetApiKeyProps = { */ export type GetLogsProps = { /** - * First log entry to retrieve. Sorted by decreasing date with 0 being the most recent. + * First log entry to retrieve. The most recent entries are listed first. */ offset?: number; /** @@ -320,11 +320,11 @@ export type GetLogsProps = { */ length?: number; /** - * Index for which log entries should be retrieved. When omitted, log entries are retrieved for all indices. + * Index for which to retrieve log entries. By default, log entries are retrieved for all indices. */ indexName?: string; /** - * Type of log entries to retrieve. When omitted, all log entries are retrieved. + * Type of log entries to retrieve. By default, all log entries are retrieved. */ type?: LogType; }; @@ -334,15 +334,15 @@ export type GetLogsProps = { */ export type GetObjectProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** - * Unique record (object) identifier. + * Unique record identifier. */ objectID: string; /** - * Attributes to include with the records in the response. This is useful to reduce the size of the API response. By default, all retrievable attributes are returned. `objectID` is always retrieved, even when not specified. [`unretrievableAttributes`](https://www.algolia.com/doc/api-reference/api-parameters/unretrievableAttributes/) won\'t be retrieved unless the request is authenticated with the admin API key. + * Attributes to include with the records in the response. This is useful to reduce the size of the API response. By default, all retrievable attributes are returned. `objectID` is always retrieved. Attributes included in `unretrievableAttributes` won\'t be retrieved unless the request is authenticated with the admin API key. */ attributesToRetrieve?: string[]; }; @@ -352,7 +352,7 @@ export type GetObjectProps = { */ export type GetRuleProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** @@ -366,7 +366,7 @@ export type GetRuleProps = { */ export type GetSettingsProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; }; @@ -376,7 +376,7 @@ export type GetSettingsProps = { */ export type GetSynonymProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** @@ -390,7 +390,7 @@ export type GetSynonymProps = { */ export type GetTaskProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** @@ -404,7 +404,7 @@ export type GetTaskProps = { */ export type GetUserIdProps = { /** - * UserID to assign. + * User ID to assign. */ userID: string; }; @@ -414,7 +414,7 @@ export type GetUserIdProps = { */ export type HasPendingMappingsProps = { /** - * Indicates whether to include the cluster\'s pending mapping state in the response. + * Whether to include the cluster\'s pending mapping state in the response. */ getClusters?: boolean; }; @@ -424,11 +424,11 @@ export type HasPendingMappingsProps = { */ export type ListIndicesProps = { /** - * Returns the requested page number. The page size is determined by the `hitsPerPage` parameter. You can see the number of available pages in the `nbPages` response attribute. When `page` is null, the API response is not paginated. + * Requested page of the API response. If `null`, the API response is not paginated. */ page?: number; /** - * Maximum number of hits per page. + * Number of hits per page. */ hitsPerPage?: number; }; @@ -438,11 +438,11 @@ export type ListIndicesProps = { */ export type ListUserIdsProps = { /** - * Returns the requested page number. The page size is determined by the `hitsPerPage` parameter. You can see the number of available pages in the `nbPages` response attribute. When `page` is null, the API response is not paginated. + * Requested page of the API response. If `null`, the API response is not paginated. */ page?: number; /** - * Maximum number of hits per page. + * Number of hits per page. */ hitsPerPage?: number; }; @@ -452,7 +452,7 @@ export type ListUserIdsProps = { */ export type OperationIndexProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; operationIndexParams: OperationIndexParams; @@ -463,19 +463,19 @@ export type OperationIndexProps = { */ export type PartialUpdateObjectProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** - * Unique record (object) identifier. + * Unique record identifier. */ objectID: string; /** - * Object with attributes to update. + * Attributes with their values. */ attributesToUpdate: Record; /** - * Indicates whether to create a new record if it doesn\'t exist yet. + * Whether to create a new record if it doesn\'t exist. */ createIfNotExists?: boolean; }; @@ -485,7 +485,7 @@ export type PartialUpdateObjectProps = { */ export type RemoveUserIdProps = { /** - * UserID to assign. + * User ID to assign. */ userID: string; }; @@ -515,11 +515,11 @@ export type RestoreApiKeyProps = { */ export type SaveObjectProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** - * The Algolia record. + * The record, a schemaless object with attributes that are useful in the context of search and discovery. */ body: Record; }; @@ -529,7 +529,7 @@ export type SaveObjectProps = { */ export type SaveRuleProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** @@ -538,7 +538,7 @@ export type SaveRuleProps = { objectID: string; rule: Rule; /** - * Indicates whether changed index settings are forwarded to the replica indices. + * Whether changes are applied to replica indices. */ forwardToReplicas?: boolean; }; @@ -548,16 +548,16 @@ export type SaveRuleProps = { */ export type SaveRulesProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; rules: Rule[]; /** - * Indicates whether changed index settings are forwarded to the replica indices. + * Whether changes are applied to replica indices. */ forwardToReplicas?: boolean; /** - * Indicates whether existing rules should be deleted before adding this batch. + * Whether existing rules should be deleted before adding this batch. */ clearExistingRules?: boolean; }; @@ -567,7 +567,7 @@ export type SaveRulesProps = { */ export type SaveSynonymProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** @@ -576,7 +576,7 @@ export type SaveSynonymProps = { objectID: string; synonymHit: SynonymHit; /** - * Indicates whether changed index settings are forwarded to the replica indices. + * Whether changes are applied to replica indices. */ forwardToReplicas?: boolean; }; @@ -586,16 +586,16 @@ export type SaveSynonymProps = { */ export type SaveSynonymsProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; synonymHit: SynonymHit[]; /** - * Indicates whether changed index settings are forwarded to the replica indices. + * Whether changes are applied to replica indices. */ forwardToReplicas?: boolean; /** - * Indicates whether to replace all synonyms in the index with the ones sent with this request. + * Whether to replace all synonyms in the index with the ones sent with this request. */ replaceExistingSynonyms?: boolean; }; @@ -637,7 +637,7 @@ export type LegacySearchMethodProps = LegacySearchQuery[]; */ export type SearchDictionaryEntriesProps = { /** - * Dictionary to search in. + * Dictionary type in which to search. */ dictionaryName: DictionaryType; searchDictionaryEntriesParams: SearchDictionaryEntriesParams; @@ -648,11 +648,11 @@ export type SearchDictionaryEntriesProps = { */ export type SearchForFacetValuesProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** - * Facet name. + * Facet attribute in which to search for values. This attribute must be included in the `attributesForFaceting` index setting with the `searchable()` modifier. */ facetName: string; searchForFacetValuesRequest?: SearchForFacetValuesRequest; @@ -663,7 +663,7 @@ export type SearchForFacetValuesProps = { */ export type SearchRulesProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; searchRulesParams?: SearchRulesParams; @@ -674,7 +674,7 @@ export type SearchRulesProps = { */ export type SearchSingleIndexProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; searchParams?: SearchParams; @@ -685,7 +685,7 @@ export type SearchSingleIndexProps = { */ export type SearchSynonymsProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** @@ -699,12 +699,12 @@ export type SearchSynonymsProps = { */ export type SetSettingsProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; indexSettings: IndexSettings; /** - * Indicates whether changed index settings are forwarded to the replica indices. + * Whether changes are applied to replica indices. */ forwardToReplicas?: boolean; }; diff --git a/packages/client-search/model/condition.ts b/packages/client-search/model/condition.ts index bb600e8c4..fea1e6776 100644 --- a/packages/client-search/model/condition.ts +++ b/packages/client-search/model/condition.ts @@ -4,19 +4,24 @@ import type { Anchoring } from './anchoring'; export type Condition = { /** - * Query pattern syntax. + * Query pattern that triggers the rule. You can use either a literal string, or a special pattern `{facet:ATTRIBUTE}`, where `ATTRIBUTE` is a facet name. The rule is triggered if the query matches the literal string or a value of the specified facet. For example, with `pattern: {facet:genre}`, the rule is triggered when users search for a genre, such as \"comedy\". */ pattern?: string; anchoring?: Anchoring; /** - * Whether the pattern matches on plurals, synonyms, and typos. + * Whether the pattern should match plurals, synonyms, and typos. */ alternatives?: boolean; /** - * Rule context format: [A-Za-z0-9_-]+). + * An additional restriction that only triggers the rule, when the search has the same value as `ruleContexts` parameter. For example, if `context: mobile`, the rule is only triggered when the search request has a matching `ruleContexts: mobile`. A rule context must only contain alphanumeric characters. */ context?: string; + + /** + * Filters that trigger the rule. You can add add filters using the syntax `facet:value` so that the rule is triggered, when the specific filter is selected. You can use `filters` on its own or combine it with the `pattern` parameter. + */ + filters?: string; }; diff --git a/packages/client-search/model/consequence.ts b/packages/client-search/model/consequence.ts index be9aa688d..a24c7e3a8 100644 --- a/packages/client-search/model/consequence.ts +++ b/packages/client-search/model/consequence.ts @@ -5,28 +5,28 @@ import type { ConsequenceParams } from './consequenceParams'; import type { Promote } from './promote'; /** - * [Consequences](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/#consequences) of a rule. + * Effect of the rule. For more information, see [Consequences](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/#consequences). */ export type Consequence = { params?: ConsequenceParams; /** - * Records to promote. + * Records you want to pin to a specific position in the search results. You can promote up to 300 records, either individually, or as groups of up to 100 records each. */ promote?: Promote[]; /** - * Only use in combination with the `promote` consequence. When `true`, promoted results will be restricted to match the filters of the current search. When `false`, the promoted results will show up regardless of the filters. + * Whether promoted records must match an active filter for the consequence to be applied. This ensures that user actions (filtering the search) are given a higher precendence. For example, if you promote a record with the `color: red` attribute, and the user filters the search for `color: blue`, the \"red\" record won\'t be shown. */ filterPromotes?: boolean; /** - * Records to hide. By default, you can hide up to 50 records per rule. + * Records you want to hide from the search results. */ hide?: ConsequenceHide[]; /** - * Custom JSON object that will be appended to the userData array in the response. This object isn\'t interpreted by the API. It\'s limited to 1kB of minified JSON. + * A JSON object with custom data that will be appended to the `userData` array in the response. This object isn\'t interpreted by the API and is limited to 1 kB of minified JSON. */ userData?: any | null; }; diff --git a/packages/client-search/model/consequenceHide.ts b/packages/client-search/model/consequenceHide.ts index ff8731ed7..9ef5cf251 100644 --- a/packages/client-search/model/consequenceHide.ts +++ b/packages/client-search/model/consequenceHide.ts @@ -1,11 +1,11 @@ // 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. /** - * Unique identifier of the record to hide. + * Object ID of the record to hide. */ export type ConsequenceHide = { /** - * Unique object identifier. + * Unique record identifier. */ objectID: string; }; diff --git a/packages/client-search/model/consequenceQuery.ts b/packages/client-search/model/consequenceQuery.ts index 464cb5325..28d8722a3 100644 --- a/packages/client-search/model/consequenceQuery.ts +++ b/packages/client-search/model/consequenceQuery.ts @@ -3,6 +3,6 @@ import type { ConsequenceQueryObject } from './consequenceQueryObject'; /** - * When providing a string, it replaces the entire query string. When providing an object, it describes incremental edits to be made to the query string (but you can\'t do both). + * Replace or edit the search query. If `consequenceQuery` is a string, the entire search query is replaced with that string. If `consequenceQuery` is an object, it describes incremental edits made to the query. */ export type ConsequenceQuery = ConsequenceQueryObject | string; diff --git a/packages/client-search/model/consequenceQueryObject.ts b/packages/client-search/model/consequenceQueryObject.ts index 4aedb781e..6d12dbc8a 100644 --- a/packages/client-search/model/consequenceQueryObject.ts +++ b/packages/client-search/model/consequenceQueryObject.ts @@ -4,12 +4,12 @@ import type { Edit } from './edit'; export type ConsequenceQueryObject = { /** - * Words to remove. + * Words to remove from the search query. */ remove?: string[]; /** - * Edits to apply. + * Changes to make to the search query. */ edits?: Edit[]; }; diff --git a/packages/client-search/model/createdAtResponse.ts b/packages/client-search/model/createdAtResponse.ts index 23e13dc05..75ab8fe31 100644 --- a/packages/client-search/model/createdAtResponse.ts +++ b/packages/client-search/model/createdAtResponse.ts @@ -5,7 +5,7 @@ */ export type CreatedAtResponse = { /** - * Timestamp of creation in [ISO-8601](https://wikipedia.org/wiki/ISO_8601) format. + * Timestamp of creation in [ISO 8601](https://wikipedia.org/wiki/ISO_8601) format. */ createdAt: string; }; diff --git a/packages/client-search/model/cursor.ts b/packages/client-search/model/cursor.ts index b645bb3aa..db36a6129 100644 --- a/packages/client-search/model/cursor.ts +++ b/packages/client-search/model/cursor.ts @@ -2,7 +2,7 @@ export type Cursor = { /** - * Cursor indicating the location to resume browsing from. Must match the value returned by the previous call. Pass this value to the subsequent browse call to get the next page of results. When the end of the index has been reached, `cursor` is absent from the response. + * Cursor to get the next page of the response. The parameter must match the value returned in the response of a previous request. The last page of the response does not return a `cursor` attribute. */ cursor?: string; }; diff --git a/packages/client-search/model/deleteByParams.ts b/packages/client-search/model/deleteByParams.ts index 776c9c8d3..ff6681d83 100644 --- a/packages/client-search/model/deleteByParams.ts +++ b/packages/client-search/model/deleteByParams.ts @@ -9,7 +9,7 @@ export type DeleteByParams = { facetFilters?: FacetFilters; /** - * [Filter](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering/) the query with numeric, facet, or tag filters. + * Filter the search so that only records with matching values are included in the results. These filters are supported: - **Numeric filters.** ` `, where `` is one of `<`, `<=`, `=`, `!=`, `>`, `>=`. - **Ranges.** `: TO ` where `` and `` are the lower and upper limits of the range (inclusive). - **Facet filters.** `:` where `` is a facet attribute (case-sensitive) and `` a facet value. - **Tag filters.** `_tags:` or just `` (case-sensitive). - **Boolean filters.** `: 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; @@ -18,19 +18,19 @@ export type DeleteByParams = { tagFilters?: TagFilters; /** - * Search for entries [around a central location](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filter-around-a-central-point), enabling a geographical search within a circular area. + * Coordinates for the center of a circle, expressed as a comma-separated string of latitude and longitude. Only records included within 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; aroundRadius?: AroundRadius; /** - * Search inside a [rectangular area](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas) (in geographical coordinates). + * 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?: number[][]; /** - * Search inside a [polygon](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas) (in geographical coordinates). + * 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?: number[][]; }; diff --git a/packages/client-search/model/deletedAtResponse.ts b/packages/client-search/model/deletedAtResponse.ts index 58a016bde..f8ae3d95d 100644 --- a/packages/client-search/model/deletedAtResponse.ts +++ b/packages/client-search/model/deletedAtResponse.ts @@ -5,7 +5,7 @@ */ export type DeletedAtResponse = { /** - * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the `task` operation and this `taskID`. + * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the [`task` operation](#tag/Indices/operation/getTask) and this `taskID`. */ taskID: number; diff --git a/packages/client-search/model/dictionaryEntry.ts b/packages/client-search/model/dictionaryEntry.ts index 807f90270..2a832ca4b 100644 --- a/packages/client-search/model/dictionaryEntry.ts +++ b/packages/client-search/model/dictionaryEntry.ts @@ -7,27 +7,27 @@ import type { DictionaryEntryState } from './dictionaryEntryState'; */ export type DictionaryEntry = Record & { /** - * Unique identifier for a dictionary object. + * Unique identifier for the dictionary entry. */ objectID: string; /** - * [Supported language ISO code](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages/). + * ISO code of a [supported language](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages/). */ language: string; /** - * Dictionary entry word. Usage depends on the type of dictionary entry. **`stopwordEntry`** The stop word you want to add or update. If the entry already exists in Algolia\'s standard dictionary, you can override its behavior by adding it to the custom dictionary and setting its `state` to `disabled`. **`compoundEntry`** When `decomposition` is empty: adds `word` as a compound atom. For example, atom “kino” decomposes the query “kopfkino” into \"kopf\" and \"kino\". When `decomposition` isn\'t empty: creates a decomposition exception. For example, when decomposition is set to the [\"hund\", \"hutte\"] exception, \"hundehutte\" decomposes into “hund” and “hutte”, discarding the linking \"e\". + * Matching dictionary word for `stopwords` and `compounds` dictionaries. */ word?: string; /** - * Compound dictionary [word declensions](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/how-to/customize-plurals-and-other-declensions/). If the entry already exists in Algolia\'s standard dictionary, you can override its behavior by adding it to the custom dictionary and setting its `state` to `disabled`. + * Matching words in the `plurals` dictionary including declensions. */ words?: string[]; /** - * For compound entries, governs the behavior of the `word` parameter. + * Invividual components of a compound word in the `compounds` dictionary. */ decomposition?: string[]; diff --git a/packages/client-search/model/dictionaryEntryState.ts b/packages/client-search/model/dictionaryEntryState.ts index 785180236..5ea78345d 100644 --- a/packages/client-search/model/dictionaryEntryState.ts +++ b/packages/client-search/model/dictionaryEntryState.ts @@ -1,6 +1,6 @@ // 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. /** - * Indicates whether a dictionary entry is active (`enabled`) or inactive (`disabled`). + * Whether a dictionary entry is active. */ export type DictionaryEntryState = 'disabled' | 'enabled'; diff --git a/packages/client-search/model/dictionaryLanguage.ts b/packages/client-search/model/dictionaryLanguage.ts index 4335e2cfe..7858762a1 100644 --- a/packages/client-search/model/dictionaryLanguage.ts +++ b/packages/client-search/model/dictionaryLanguage.ts @@ -1,11 +1,11 @@ // 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. /** - * Custom entries for a dictionary. + * Dictionary type. If `null`, this dictionary type isn\'t supported for the language. */ export type DictionaryLanguage = { /** - * If `0`, the dictionary hasn\'t been customized and only contains standard entries provided by Algolia. If `null`, that feature isn\'t available or isn\'t supported for that language. + * Number of custom dictionary entries. */ nbCustomEntries?: number; }; diff --git a/packages/client-search/model/dictionarySettingsParams.ts b/packages/client-search/model/dictionarySettingsParams.ts index 67021c7fc..053d5e85d 100644 --- a/packages/client-search/model/dictionarySettingsParams.ts +++ b/packages/client-search/model/dictionarySettingsParams.ts @@ -3,7 +3,7 @@ import type { StandardEntries } from './standardEntries'; /** - * Enable or turn off the built-in Algolia stop words for a specific language. + * Turn on or off the built-in Algolia stop words for a specific language. */ export type DictionarySettingsParams = { disableStandardEntries: StandardEntries; diff --git a/packages/client-search/model/distinct.ts b/packages/client-search/model/distinct.ts index 1779d9741..dc87dfb00 100644 --- a/packages/client-search/model/distinct.ts +++ b/packages/client-search/model/distinct.ts @@ -1,6 +1,6 @@ // 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. /** - * Enables [deduplication or grouping of results (Algolia\'s _distinct_ feature](https://www.algolia.com/doc/guides/managing-results/refine-results/grouping/#introducing-algolias-distinct-feature)). + * Determines how many records of a group are included in the search results. Records with the same value for the `attributeForDistinct` attribute are considered a group. The `distinct` setting controls how many members of the group are returned. This is useful for [deduplication and grouping](https://www.algolia.com/doc/guides/managing-results/refine-results/grouping/#introducing-algolias-distinct-feature). The `distinct` setting is ignored if `attributeForDistinct` is not set. */ export type Distinct = boolean | number; diff --git a/packages/client-search/model/edit.ts b/packages/client-search/model/edit.ts index 9c11afef4..b77d006e3 100644 --- a/packages/client-search/model/edit.ts +++ b/packages/client-search/model/edit.ts @@ -11,7 +11,7 @@ export type Edit = { delete?: string; /** - * Text that should be inserted in place of the removed text inside the query string. + * Text to be added in place of the deleted text inside the query string. */ insert?: string; }; diff --git a/packages/client-search/model/exactOnSingleWordQuery.ts b/packages/client-search/model/exactOnSingleWordQuery.ts index 6d5747887..bad4a2bae 100644 --- a/packages/client-search/model/exactOnSingleWordQuery.ts +++ b/packages/client-search/model/exactOnSingleWordQuery.ts @@ -1,6 +1,6 @@ // 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. /** - * Determines how 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) is computed when the query contains only one word. + * Determines how 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) is computed when the search query has only one word.
attribute
The Exact ranking criterion is 1 if the query word and attribute value are the same. For example, a search for \"road\" will match the value \"road\", but not \"road trip\".
none
The Exact ranking criterion is ignored on single-word searches.
word
The Exact ranking criterion is 1 if the query word is found in the attribute value. The query word must have at least 3 characters and must not be a stop word.
If `exactOnSingleWordQuery` is `word`, only exact matches will be highlighted, partial and prefix matches won\'t. */ export type ExactOnSingleWordQuery = 'attribute' | 'none' | 'word'; diff --git a/packages/client-search/model/facetFilters.ts b/packages/client-search/model/facetFilters.ts index e9eae1db3..f83f2eea3 100644 --- a/packages/client-search/model/facetFilters.ts +++ b/packages/client-search/model/facetFilters.ts @@ -3,6 +3,6 @@ import type { MixedSearchFilters } from './mixedSearchFilters'; /** - * [Filter hits by facet value](https://www.algolia.com/doc/api-reference/api-parameters/facetFilters/). + * Filter the search by facet values, so that only records with the same facet values are retrieved. **Prefer using the `filters` parameter, which supports all filter types and combinations with boolean operators.** - `[filter1, filter2]` is interpreted as `filter1 AND filter2`. - `[[filter1, filter2], filter3]` is interpreted as `filter1 OR filter2 AND filter3`. - `facet:-value` is interpreted as `NOT facet:value`. While it\'s best to avoid attributes that start with a `-`, you can still filter them by escaping with a backslash: `facet:\\-value`. */ export type FacetFilters = MixedSearchFilters[] | string; diff --git a/packages/client-search/model/facetHits.ts b/packages/client-search/model/facetHits.ts index 06d0ffb9c..bd205a61e 100644 --- a/packages/client-search/model/facetHits.ts +++ b/packages/client-search/model/facetHits.ts @@ -7,12 +7,12 @@ export type FacetHits = { value: string; /** - * Markup text with `facetQuery` matches highlighted. + * Highlighted attribute value, including HTML tags. */ highlighted: string; /** - * Number of records containing this facet value. This takes into account the extra search parameters specified in the query. Like for a regular search query, the [counts may not be exhaustive](https://support.algolia.com/hc/en-us/articles/4406975248145-Why-are-my-facet-and-hit-counts-not-accurate-). + * Number of records with this facet value. [The count may be approximated](https://support.algolia.com/hc/en-us/articles/4406975248145-Why-are-my-facet-and-hit-counts-not-accurate-). */ count: number; }; diff --git a/packages/client-search/model/facetOrdering.ts b/packages/client-search/model/facetOrdering.ts index 4e1af92fd..9e057ded5 100644 --- a/packages/client-search/model/facetOrdering.ts +++ b/packages/client-search/model/facetOrdering.ts @@ -4,13 +4,13 @@ import type { Facets } from './facets'; import type { Value } from './value'; /** - * Defines the ordering of facets (widgets). + * Order of facet names and facet values in your UI. */ export type FacetOrdering = { facets?: Facets; /** - * Ordering of facet values within an individual facet. + * Order of facet values. One object for each facet. */ values?: Record; }; diff --git a/packages/client-search/model/facets.ts b/packages/client-search/model/facets.ts index b10eb0f3c..3aefad3a5 100644 --- a/packages/client-search/model/facets.ts +++ b/packages/client-search/model/facets.ts @@ -1,11 +1,11 @@ // 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. /** - * Ordering of facets (widgets). + * Order of facet names. */ export type Facets = { /** - * Pinned order of facet lists. + * Explicit order of facets or facet values. This setting lets you always show specific facets or facet values at the top of the list. */ order?: string[]; }; diff --git a/packages/client-search/model/getObjectsRequest.ts b/packages/client-search/model/getObjectsRequest.ts index a2124fbff..f1281a71a 100644 --- a/packages/client-search/model/getObjectsRequest.ts +++ b/packages/client-search/model/getObjectsRequest.ts @@ -1,7 +1,7 @@ // 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. /** - * Record retrieval operation. + * Request body for retrieving records. */ export type GetObjectsRequest = { /** @@ -10,12 +10,12 @@ export type GetObjectsRequest = { attributesToRetrieve?: string[]; /** - * Record\'s objectID. + * Object ID for the record to retrieve. */ objectID: string; /** - * Name of the index containing the required records. + * Index from which to retrieve the records. */ indexName: string; }; diff --git a/packages/client-search/model/getObjectsResponse.ts b/packages/client-search/model/getObjectsResponse.ts index 4e7dd7abe..f69e6c756 100644 --- a/packages/client-search/model/getObjectsResponse.ts +++ b/packages/client-search/model/getObjectsResponse.ts @@ -2,7 +2,7 @@ export type GetObjectsResponse> = { /** - * Retrieved results. + * Retrieved records. */ results: T[]; }; diff --git a/packages/client-search/model/hasPendingMappingsResponse.ts b/packages/client-search/model/hasPendingMappingsResponse.ts index 1a5421899..e4eedf62b 100644 --- a/packages/client-search/model/hasPendingMappingsResponse.ts +++ b/packages/client-search/model/hasPendingMappingsResponse.ts @@ -2,7 +2,7 @@ export type HasPendingMappingsResponse = { /** - * Indicates whether there are clusters undergoing migration, creation, or deletion. + * Whether there are clusters undergoing migration, creation, or deletion. */ pending: boolean; diff --git a/packages/client-search/model/highlightResultOption.ts b/packages/client-search/model/highlightResultOption.ts index 7d68dce0e..0de083fe2 100644 --- a/packages/client-search/model/highlightResultOption.ts +++ b/packages/client-search/model/highlightResultOption.ts @@ -3,18 +3,18 @@ import type { MatchLevel } from './matchLevel'; /** - * Show highlighted section and words matched on a query. + * Surround words that match the query with HTML tags for highlighting. */ export type HighlightResultOption = { /** - * Markup text with `facetQuery` matches highlighted. + * Highlighted attribute value, including HTML tags. */ value: string; matchLevel: MatchLevel; /** - * List of words from the query that matched the object. + * List of matched words from the search query. */ matchedWords: string[]; diff --git a/packages/client-search/model/hit.ts b/packages/client-search/model/hit.ts index d670f4df4..9c0028146 100644 --- a/packages/client-search/model/hit.ts +++ b/packages/client-search/model/hit.ts @@ -5,21 +5,21 @@ import type { RankingInfo } from './rankingInfo'; import type { SnippetResult } from './snippetResult'; /** - * A single hit. + * Search result. A hit is a record from your index, augmented with special attributes for highlighting, snippeting, and ranking. */ export type Hit> = T & { /** - * Unique object identifier. + * Unique record identifier. */ objectID: string; /** - * Show highlighted section and words matched on a query. + * Surround words that match the query with HTML tags for highlighting. */ _highlightResult?: Record; /** - * Snippeted attributes show parts of the matched attributes. Only returned when attributesToSnippet is non-empty. + * Snippets that show the context around a matching search query. */ _snippetResult?: Record; diff --git a/packages/client-search/model/ignorePlurals.ts b/packages/client-search/model/ignorePlurals.ts index ffea12b13..e02272856 100644 --- a/packages/client-search/model/ignorePlurals.ts +++ b/packages/client-search/model/ignorePlurals.ts @@ -1,6 +1,6 @@ // 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. /** - * Treats singular, plurals, and other forms of declensions as matching terms. `ignorePlurals` is used in conjunction with the `queryLanguages` setting. _list_: language ISO codes for which ignoring plurals should be enabled. This list will override any values that you may have set in `queryLanguages`. _true_: enables the ignore plurals feature, where singulars and plurals are considered equivalent (\"foot\" = \"feet\"). The languages supported here are either [every language](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages/) (this is the default) or those set by `queryLanguages`. _false_: turns off the ignore plurals feature, so that singulars and plurals aren\'t considered to be the same (\"foot\" will not find \"feet\"). + * Treat singular, plurals, and other forms of declensions as equivalent. You should only use this feature for the languages used in your index. */ export type IgnorePlurals = string[] | boolean; diff --git a/packages/client-search/model/index.ts b/packages/client-search/model/index.ts index edfc46102..2174f5bda 100644 --- a/packages/client-search/model/index.ts +++ b/packages/client-search/model/index.ts @@ -117,6 +117,7 @@ export * from './saveObjectResponse'; export * from './saveSynonymResponse'; export * from './scopeType'; export * from './searchDictionaryEntriesParams'; +export * from './searchDictionaryEntriesResponse'; export * from './searchForFacetValuesRequest'; export * from './searchForFacetValuesResponse'; export * from './searchForFacets'; diff --git a/packages/client-search/model/indexSettings.ts b/packages/client-search/model/indexSettings.ts index 4ef41b83d..7f2e9acde 100644 --- a/packages/client-search/model/indexSettings.ts +++ b/packages/client-search/model/indexSettings.ts @@ -4,6 +4,6 @@ import type { BaseIndexSettings } from './baseIndexSettings'; import type { IndexSettingsAsSearchParams } from './indexSettingsAsSearchParams'; /** - * Algolia index settings. + * Index settings. */ export type IndexSettings = BaseIndexSettings & IndexSettingsAsSearchParams; diff --git a/packages/client-search/model/indexSettingsAsSearchParams.ts b/packages/client-search/model/indexSettingsAsSearchParams.ts index 765e380d1..b946517d8 100644 --- a/packages/client-search/model/indexSettingsAsSearchParams.ts +++ b/packages/client-search/model/indexSettingsAsSearchParams.ts @@ -16,47 +16,42 @@ import type { TypoTolerance } from './typoTolerance'; export type IndexSettingsAsSearchParams = { /** - * Attributes used for [faceting](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/) and the [modifiers](https://www.algolia.com/doc/api-reference/api-parameters/attributesForFaceting/#modifiers) that can be applied: `filterOnly`, `searchable`, and `afterDistinct`. - */ - attributesForFaceting?: string[]; - - /** - * Attributes to include in the API response. To reduce the size of your response, you can retrieve only some of the attributes. By default, the response includes all attributes. + * Attributes to include in the API response. To reduce the size of your response, you can retrieve only some of the attributes. - `*` 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?: string[]; /** - * Determines the order in which Algolia [returns your results](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/). + * 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?: string[]; /** - * Specifies the [Custom ranking criterion](https://www.algolia.com/doc/guides/managing-results/must-do/custom-ranking/). Use the `asc` and `desc` modifiers to specify the ranking order: ascending or descending. + * Attributes to use as [custom ranking](https://www.algolia.com/doc/guides/managing-results/must-do/custom-ranking/). The custom ranking attributes decide which items are shown first if the other ranking criteria are equal. Records with missing values for your selected custom ranking attributes are always sorted last. Boolean attributes are sorted based on their alphabetical order. **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.
If you use two or more custom ranking attributes, [reduce the precision](https://www.algolia.com/doc/guides/managing-results/must-do/custom-ranking/how-to/controlling-custom-ranking-metrics-precision/) of your first attributes, or the other attributes will never be applied. */ customRanking?: string[]; /** - * Relevancy threshold below which less relevant results aren\'t included in the results. + * 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. Strings that match the search query in the attributes are highlighted by surrounding them with HTML tags (`highlightPreTag` and `highlightPostTag`). + * Attributes to highlight. By default, all searchable attributes are highlighted. Use `*` to highlight all attributes or use an empty array `[]` to turn off highlighting. 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?: string[]; /** - * Attributes to _snippet_. \'Snippeting\' is shortening the attribute to a certain number of words. If not specified, the attribute is shortened to the 10 words around the matching string but you can specify the number. For example: `body:20`. + * Attributes for which to enable snippets. 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?: string[]; /** - * HTML string to insert before the highlighted parts in all highlight and snippet results. + * HTML tag to insert before the highlighted parts in all highlighted results and snippets. */ highlightPreTag?: string; /** - * HTML string to insert after the highlighted parts in all highlight and snippet results. + * HTML tag to insert after the highlighted parts in all highlighted results and snippets. */ highlightPostTag?: string; @@ -66,7 +61,7 @@ export type IndexSettingsAsSearchParams = { snippetEllipsisText?: string; /** - * Restrict highlighting and snippeting to items that matched the query. + * 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; @@ -76,24 +71,24 @@ export type IndexSettingsAsSearchParams = { hitsPerPage?: number; /** - * Minimum number of characters a word in the query string 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). + * 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 query string 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). + * 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 (\"numeric tokens\") in the query string. + * 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/). + * Attributes for which you want to turn off [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/). 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?: string[]; @@ -102,27 +97,27 @@ export type IndexSettingsAsSearchParams = { removeStopWords?: RemoveStopWords; /** - * Characters that the engine shouldn\'t automatically [normalize](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/normalization/). + * Characters for which diacritics should be preserved. By default, Algolia removes diacritics from letters. For example, `é` becomes `e`. If this causes issues in your search, you can specify characters that should keep their diacritics. */ keepDiacriticsOnCharacters?: string; /** - * Sets your user\'s search language. This adjusts language-specific settings and features such as `ignorePlurals`, `removeStopWords`, and [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) word detection. + * [ISO code](https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes) for language-specific settings such as plurals, stop words, 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?: string[]; /** - * [Splits compound words](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/#splitting-compound-words) into their component word parts in the query. + * Whether to split compound words 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. */ decompoundQuery?: boolean; /** - * Incidates whether [Rules](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/) are enabled. + * Whether to enable rules. */ enableRules?: boolean; /** - * Incidates whether [Personalization](https://www.algolia.com/doc/guides/personalization/what-is-personalization/) is enabled. + * Whether to enable Personalization. */ enablePersonalization?: boolean; @@ -135,51 +130,51 @@ export type IndexSettingsAsSearchParams = { semanticSearch?: SemanticSearch; /** - * Enables the [advanced query syntax](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/#advanced-syntax). + * Whether to support phrase matching and excluding words from search queries. Use the `advancedSyntaxFeatures` parameter to control which feature is supported. */ advancedSyntax?: boolean; /** - * Words which should be considered [optional](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/#creating-a-list-of-optional-words) when found in a query. + * 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 dividied 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?: string[]; /** - * 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). + * 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). This can be useful for attributes with long values, where the likelyhood 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?: string[]; exactOnSingleWordQuery?: ExactOnSingleWordQuery; /** - * Alternatives that should be considered an exact match by [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). + * 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.
. */ alternativesAsExact?: AlternativesAsExact[]; /** - * Allows you to specify which advanced syntax features are active when `advancedSyntax` is enabled. + * 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?: AdvancedSyntaxFeatures[]; distinct?: Distinct; /** - * Whether to highlight and snippet the original word that matches the synonym or the synonym itself. + * 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 occurences of \"house\" are replaced by \"home\" in the highlighted response. */ replaceSynonymsInHighlight?: boolean; /** - * Precision of the [proximity ranking criterion](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#proximity). + * 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; /** - * Attributes to include in the API response for search and browse queries. + * 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?: string[]; /** - * Maximum number of facet hits to return when [searching for facet values](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#search-for-facet-values). + * 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; @@ -189,19 +184,19 @@ export type IndexSettingsAsSearchParams = { maxValuesPerFacet?: number; /** - * Controls how facet values are fetched. + * 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; /** - * When the [Attribute criterion is ranked above Proximity](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#attribute-and-proximity-combinations) in your ranking formula, Proximity is used to select which searchable attribute is matched in the Attribute ranking stage. + * 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; /** - * Indicates whether this search will use [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking/). + * 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; diff --git a/packages/client-search/model/log.ts b/packages/client-search/model/log.ts index 6a6332a8e..becb94206 100644 --- a/packages/client-search/model/log.ts +++ b/packages/client-search/model/log.ts @@ -4,32 +4,32 @@ import type { LogQuery } from './logQuery'; export type Log = { /** - * Timestamp in [ISO 8601](https://wikipedia.org/wiki/ISO_8601) format. + * Timestamp of the API request in ISO 8601 format. */ timestamp: string; /** - * HTTP method of the performed request. + * HTTP method of the request. */ method: string; /** - * HTTP response code. + * HTTP status code of the response. */ answer_code: string; /** - * Request body. Truncated after 1,000 characters. + * Request body. */ query_body: string; /** - * Answer body. Truncated after 1,000 characters. + * Response body. */ answer: string; /** - * Request URL. + * URL of the API endpoint. */ url: string; @@ -39,7 +39,7 @@ export type Log = { ip: string; /** - * Request headers (API key is obfuscated). + * Request headers (API keys are obfuscated). */ query_headers: string; @@ -49,12 +49,12 @@ export type Log = { sha1: string; /** - * Number of API calls. + * Number of API requests. */ nb_api_calls: string; /** - * Processing time for the query. Doesn\'t include network time. + * Processing time for the query in milliseconds. This doesn\'t include latency due to the network. */ processing_time_ms: string; @@ -69,12 +69,12 @@ export type Log = { query_params?: string; /** - * Number of hits returned for the query. + * Number of search results (hits) returned for the query. */ query_nb_hits?: string; /** - * Performed queries for the given request. + * Queries performed for the given request. */ inner_queries?: LogQuery[]; }; diff --git a/packages/client-search/model/logQuery.ts b/packages/client-search/model/logQuery.ts index aa2456008..c821e3d69 100644 --- a/packages/client-search/model/logQuery.ts +++ b/packages/client-search/model/logQuery.ts @@ -7,7 +7,7 @@ export type LogQuery = { index_name?: string; /** - * User identifier. + * A user identifier. */ user_token?: string; diff --git a/packages/client-search/model/matchLevel.ts b/packages/client-search/model/matchLevel.ts index 771daa1fe..a5fa02991 100644 --- a/packages/client-search/model/matchLevel.ts +++ b/packages/client-search/model/matchLevel.ts @@ -1,6 +1,6 @@ // 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. /** - * Indicates how well the attribute matched the search query. + * Whether the whole query string matches or only a part. */ export type MatchLevel = 'full' | 'none' | 'partial'; diff --git a/packages/client-search/model/mode.ts b/packages/client-search/model/mode.ts index 128d51a2b..37ed88734 100644 --- a/packages/client-search/model/mode.ts +++ b/packages/client-search/model/mode.ts @@ -1,6 +1,6 @@ // 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. /** - * Search mode the index will use to query for results. + * Search mode the index will use to query for results. This setting only applies to indices, for which Algolia enabled NeuralSearch for you. */ export type Mode = 'keywordSearch' | 'neuralSearch'; diff --git a/packages/client-search/model/multipleBatchResponse.ts b/packages/client-search/model/multipleBatchResponse.ts index a38ad8200..617d830bb 100644 --- a/packages/client-search/model/multipleBatchResponse.ts +++ b/packages/client-search/model/multipleBatchResponse.ts @@ -2,12 +2,12 @@ export type MultipleBatchResponse = { /** - * TaskIDs per index. + * Task IDs. One for each index. */ taskID: Record; /** - * Unique object (record) identifiers. + * Unique record identifiers. */ objectIDs: string[]; }; diff --git a/packages/client-search/model/numericFilters.ts b/packages/client-search/model/numericFilters.ts index dde128ffc..3db0c89dc 100644 --- a/packages/client-search/model/numericFilters.ts +++ b/packages/client-search/model/numericFilters.ts @@ -3,6 +3,6 @@ import type { MixedSearchFilters } from './mixedSearchFilters'; /** - * [Filter on numeric attributes](https://www.algolia.com/doc/api-reference/api-parameters/numericFilters/). + * Filter by numeric facets. **Prefer using the `filters` parameter, which supports all filter types and combinations with boolean operators.** You can use numeric comparison operators: `<`, `<=`, `=`, `!=`, `>`, `>=`. Comparsions are precise up to 3 decimals. You can also provide ranges: `facet: TO `. The range includes the lower and upper boundaries. The same combination rules apply as for `facetFilters`. */ export type NumericFilters = MixedSearchFilters[] | string; diff --git a/packages/client-search/model/operationIndexParams.ts b/packages/client-search/model/operationIndexParams.ts index 33c36066d..83644f304 100644 --- a/packages/client-search/model/operationIndexParams.ts +++ b/packages/client-search/model/operationIndexParams.ts @@ -7,12 +7,12 @@ export type OperationIndexParams = { operation: OperationType; /** - * Algolia index name. + * Index name. */ destination: string; /** - * **This only applies to the _copy_ operation.** If you omit `scope`, the copy command copies all records, settings, synonyms, and rules. If you specify `scope`, only the specified scopes are copied. + * **Only for copying.** If you specify a scope, only the selected scopes are copied. Records and the other scopes are left unchanged. If you omit the `scope` parameter, everything is copied: records, settings, synonyms, and rules. */ scope?: ScopeType[]; }; diff --git a/packages/client-search/model/operationType.ts b/packages/client-search/model/operationType.ts index 4674a69e0..3b22cc054 100644 --- a/packages/client-search/model/operationType.ts +++ b/packages/client-search/model/operationType.ts @@ -1,6 +1,6 @@ // 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. /** - * Operation to perform (_move_ or _copy_). + * Operation to perform on the index. */ export type OperationType = 'copy' | 'move'; diff --git a/packages/client-search/model/optionalFilters.ts b/packages/client-search/model/optionalFilters.ts index 1836d9315..f910cd0cf 100644 --- a/packages/client-search/model/optionalFilters.ts +++ b/packages/client-search/model/optionalFilters.ts @@ -3,6 +3,6 @@ import type { MixedSearchFilters } from './mixedSearchFilters'; /** - * Create filters to boost or demote records. Records that match the filter are ranked higher for positive and lower for negative optional filters. In contrast to regular filters, records that don\'t match the optional filter are still included in the results, only their ranking is affected. + * Filters to promote or demote records in the search results. Optional filters work like facet filters, but they don\'t exclude records from the search results. Records that match the optional filter rank before records that don\'t match. If you\'re using a negative filter `facet:-value`, matching records rank after records that don\'t match. - Optional filters don\'t work on virtual replicas. - Optional filters are applied _after_ sort-by attributes. - Optional filters don\'t work with numeric attributes. */ export type OptionalFilters = MixedSearchFilters[] | string; diff --git a/packages/client-search/model/params.ts b/packages/client-search/model/params.ts index dff37195c..8dbd02c2f 100644 --- a/packages/client-search/model/params.ts +++ b/packages/client-search/model/params.ts @@ -5,7 +5,7 @@ import type { ConsequenceQuery } from './consequenceQuery'; import type { RenderingContent } from './renderingContent'; /** - * Additional search parameters. + * Parameters to apply to this search. You can use all search parameters, plus special `automaticFacetFilters`, `automaticOptionalFacetFilters`, and `query`. */ export type Params = { query?: ConsequenceQuery; diff --git a/packages/client-search/model/promoteObjectID.ts b/packages/client-search/model/promoteObjectID.ts index aeb5e5e29..6e2f37992 100644 --- a/packages/client-search/model/promoteObjectID.ts +++ b/packages/client-search/model/promoteObjectID.ts @@ -5,12 +5,12 @@ */ export type PromoteObjectID = { /** - * Unique identifier of the record to promote. + * Unique record identifier. */ objectID: string; /** - * The position to promote the records to. If you pass objectIDs, the records are placed at this position as a group. For example, if you pronmote four objectIDs to position 0, the records take the first four positions. + * Position in the search results where you want to show the promoted records. */ position: number; }; diff --git a/packages/client-search/model/promoteObjectIDs.ts b/packages/client-search/model/promoteObjectIDs.ts index cfdaa6d76..01a5dd576 100644 --- a/packages/client-search/model/promoteObjectIDs.ts +++ b/packages/client-search/model/promoteObjectIDs.ts @@ -5,12 +5,12 @@ */ export type PromoteObjectIDs = { /** - * Unique identifiers of the records to promote. + * Object IDs of the records you want to promote. The records are placed as a group at the `position`. For example, if you want to promote four records to position `0`, they will be the first four search results. */ objectIDs: string[]; /** - * The position to promote the records to. If you pass objectIDs, the records are placed at this position as a group. For example, if you pronmote four objectIDs to position 0, the records take the first four positions. + * Position in the search results where you want to show the promoted records. */ position: number; }; diff --git a/packages/client-search/model/queryType.ts b/packages/client-search/model/queryType.ts index 50424749d..a609aca0e 100644 --- a/packages/client-search/model/queryType.ts +++ b/packages/client-search/model/queryType.ts @@ -1,6 +1,6 @@ // 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. /** - * Determines how query words are [interpreted as prefixes](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/in-depth/prefix-searching/). + * Determines if and how query words are interpreted as prefixes. By default, only the last query word is treated as prefix (`prefixLast`). To turn off prefix search, use `prefixNone`. Avoid `prefixAll`, which treats all query words as prefixes. This might lead to counterintuitive results and makes your search slower. For more information, see [Prefix searching](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/in-depth/prefix-searching/). */ export type QueryType = 'prefixAll' | 'prefixLast' | 'prefixNone'; diff --git a/packages/client-search/model/rankingInfo.ts b/packages/client-search/model/rankingInfo.ts index 71de0b00e..14edcdc59 100644 --- a/packages/client-search/model/rankingInfo.ts +++ b/packages/client-search/model/rankingInfo.ts @@ -3,14 +3,17 @@ import type { MatchedGeoLocation } from './matchedGeoLocation'; import type { Personalization } from './personalization'; +/** + * Object with detailed information about the record\'s ranking. + */ export type RankingInfo = { /** - * This field is reserved for advanced usage. + * Whether a filter matched the query. */ filters: number; /** - * Position of the most important matched attribute in the attributes to index list. + * Position of the first matched word in the best matching attribute of the record. */ firstMatchedWord: number; @@ -39,27 +42,27 @@ export type RankingInfo = { nbTypos: number; /** - * Present and set to true if a Rule promoted the hit. + * Whether the record was promoted by a rule. */ promoted: boolean; /** - * When the query contains more than one word, the sum of the distances between matched words (in meters). + * Number of words between multiple matches in the query plus 1. For single word queries, `proximityDistance` is 0. */ proximityDistance?: number; /** - * Custom ranking for the object, expressed as a single integer value. + * Overall ranking of the record, expressed as a single integer. This attribute is internal. */ userScore: number; /** - * Number of matched words, including prefixes and typos. + * Number of matched words. */ words: number; /** - * Wether the record are promoted by the re-ranking strategy. + * Whether the record is re-ranked. */ promotedByReRanking?: boolean; }; diff --git a/packages/client-search/model/reRankingApplyFilter.ts b/packages/client-search/model/reRankingApplyFilter.ts index 02a02545f..ced0223fd 100644 --- a/packages/client-search/model/reRankingApplyFilter.ts +++ b/packages/client-search/model/reRankingApplyFilter.ts @@ -3,6 +3,6 @@ import type { MixedSearchFilters } from './mixedSearchFilters'; /** - * When [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking/) is enabled, only records that match these filters will be affected by Dynamic Re-Ranking. + * Restrict [Dynamic Re-ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking/) to records that match these filters. */ export type ReRankingApplyFilter = MixedSearchFilters[] | string; diff --git a/packages/client-search/model/removeStopWords.ts b/packages/client-search/model/removeStopWords.ts index 33f66341c..9bdbf9176 100644 --- a/packages/client-search/model/removeStopWords.ts +++ b/packages/client-search/model/removeStopWords.ts @@ -1,6 +1,6 @@ // 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. /** - * Removes stop (common) words from the query before executing it. `removeStopWords` is used in conjunction with the `queryLanguages` setting. _list_: language ISO codes for which stop words should be enabled. This list will override any values that you may have set in `queryLanguages`. _true_: enables the stop words feature, ensuring that stop words are removed from consideration in a search. The languages supported here are either [every language](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages/) (this is the default) or those set by `queryLanguages`. _false_: turns off the stop words feature, allowing stop words to be taken into account in a search. + * Removes stop words from the search query. Stop words are common words like articles, conjunctions, prepositions, or pronouns that have little or no meaning on their own. In English, \"the\", \"a\", or \"and\" are stop words. You should only use this feature for the languages used in your index. */ export type RemoveStopWords = string[] | boolean; diff --git a/packages/client-search/model/removeWordsIfNoResults.ts b/packages/client-search/model/removeWordsIfNoResults.ts index 2e5b6bdef..81519af90 100644 --- a/packages/client-search/model/removeWordsIfNoResults.ts +++ b/packages/client-search/model/removeWordsIfNoResults.ts @@ -1,7 +1,7 @@ // 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. /** - * Strategy to [remove words](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/in-depth/why-use-remove-words-if-no-results/) from the query when it doesn\'t match any hits. + * Strategy for removing words from the query when it doesn\'t return any results. This helps to avoid returning empty search results.
none
No words are removed when a query doesn\'t return results.
lastWords
Treat the last (then second to last, then third to last) word as optional, until there are results or at most 5 words have been removed.
firstWords
Treat the first (then second, then third) word as optional, until there are results or at most 5 words have been removed.
allOptional
Treat all words as optional.
For more information, see [Remove words to improve results](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/in-depth/why-use-remove-words-if-no-results/). */ export type RemoveWordsIfNoResults = | 'allOptional' diff --git a/packages/client-search/model/renderingContent.ts b/packages/client-search/model/renderingContent.ts index 9c632b96e..4385efd64 100644 --- a/packages/client-search/model/renderingContent.ts +++ b/packages/client-search/model/renderingContent.ts @@ -3,7 +3,7 @@ import type { FacetOrdering } from './facetOrdering'; /** - * Extra content for the search UI, for example, to control the [ordering and display of facets](https://www.algolia.com/doc/guides/managing-results/rules/merchandising-and-promoting/how-to/merchandising-facets/#merchandise-facets-and-their-values-in-the-manual-editor). You can set a default value and dynamically override it with [Rules](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/). + * Extra data that can be used in the search UI. You can use this to control aspects of your search UI, such as, the order of facet names and values without changing your frontend code. */ export type RenderingContent = { facetOrdering?: FacetOrdering; diff --git a/packages/client-search/model/rule.ts b/packages/client-search/model/rule.ts index 77a961294..b002ec88a 100644 --- a/packages/client-search/model/rule.ts +++ b/packages/client-search/model/rule.ts @@ -9,29 +9,29 @@ import type { TimeRange } from './timeRange'; */ export type Rule = { /** - * Unique identifier for a rule object. + * Unique identifier of a rule object. */ objectID: string; /** - * [Conditions](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/#conditions) required to activate a rule. You can use up to 25 conditions per rule. + * Conditions that trigger a rule. Some consequences require specific conditions or don\'t require any condition. For more information, see [Conditions](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/#conditions). */ conditions?: Condition[]; consequence?: Consequence; /** - * Description of the rule\'s purpose. This can be helpful for display in the Algolia dashboard. + * Description of the rule\'s purpose to help you distinguish between different rules. */ description?: string; /** - * Indicates whether to enable the rule. If it isn\'t enabled, it isn\'t applied at query time. + * Whether the rule is active. */ enabled?: boolean; /** - * If you specify a validity period, the rule _only_ applies only during that period. If specified, the array must not be empty. + * Time periods when the rule is active. */ validity?: TimeRange[]; }; diff --git a/packages/client-search/model/saveObjectResponse.ts b/packages/client-search/model/saveObjectResponse.ts index f955ad1dd..cb4cbd835 100644 --- a/packages/client-search/model/saveObjectResponse.ts +++ b/packages/client-search/model/saveObjectResponse.ts @@ -2,17 +2,17 @@ export type SaveObjectResponse = { /** - * Date of creation (ISO-8601 format). + * Timestamp when the record was added, in ISO 8601 format. */ createdAt: string; /** - * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the `task` operation and this `taskID`. + * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the [`task` operation](#tag/Indices/operation/getTask) and this `taskID`. */ taskID: number; /** - * Unique object identifier. + * Unique record identifier. */ objectID?: string; }; diff --git a/packages/client-search/model/saveSynonymResponse.ts b/packages/client-search/model/saveSynonymResponse.ts index f2dddfb66..d2bc20244 100644 --- a/packages/client-search/model/saveSynonymResponse.ts +++ b/packages/client-search/model/saveSynonymResponse.ts @@ -2,7 +2,7 @@ export type SaveSynonymResponse = { /** - * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the `task` operation and this `taskID`. + * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the [`task` operation](#tag/Indices/operation/getTask) and this `taskID`. */ taskID: number; diff --git a/packages/client-search/model/searchDictionaryEntriesParams.ts b/packages/client-search/model/searchDictionaryEntriesParams.ts index b1eedbacd..035b9a14a 100644 --- a/packages/client-search/model/searchDictionaryEntriesParams.ts +++ b/packages/client-search/model/searchDictionaryEntriesParams.ts @@ -1,16 +1,16 @@ // 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. /** - * `searchDictionaryEntries` parameters. + * Search parameter. */ export type SearchDictionaryEntriesParams = { /** - * Text to search for in an index. + * Search query. */ query: string; /** - * Page to retrieve (the first page is `0`, not `1`). + * Page of search results to retrieve. */ page?: number; @@ -20,7 +20,7 @@ export type SearchDictionaryEntriesParams = { hitsPerPage?: number; /** - * [Supported language ISO code](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages/). + * ISO code of a [supported language](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages/). */ language?: string; }; diff --git a/packages/client-search/model/searchDictionaryEntriesResponse.ts b/packages/client-search/model/searchDictionaryEntriesResponse.ts new file mode 100644 index 000000000..88880a028 --- /dev/null +++ b/packages/client-search/model/searchDictionaryEntriesResponse.ts @@ -0,0 +1,25 @@ +// 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 { DictionaryEntry } from './dictionaryEntry'; + +export type SearchDictionaryEntriesResponse = { + /** + * Dictionary entries matching the search criteria. + */ + hits: DictionaryEntry[]; + + /** + * Requested page of the API response. + */ + page: number; + + /** + * Number of results (hits). + */ + nbHits: number; + + /** + * Number of pages of results. + */ + nbPages: number; +}; diff --git a/packages/client-search/model/searchForFacetValuesRequest.ts b/packages/client-search/model/searchForFacetValuesRequest.ts index 002fa62d3..03118e161 100644 --- a/packages/client-search/model/searchForFacetValuesRequest.ts +++ b/packages/client-search/model/searchForFacetValuesRequest.ts @@ -12,7 +12,7 @@ export type SearchForFacetValuesRequest = { facetQuery?: string; /** - * Maximum number of facet hits to return when [searching for facet values](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#search-for-facet-values). + * 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; }; diff --git a/packages/client-search/model/searchForFacetValuesResponse.ts b/packages/client-search/model/searchForFacetValuesResponse.ts index a842add7b..32a0189e7 100644 --- a/packages/client-search/model/searchForFacetValuesResponse.ts +++ b/packages/client-search/model/searchForFacetValuesResponse.ts @@ -3,6 +3,9 @@ import type { FacetHits } from './facetHits'; export type SearchForFacetValuesResponse = { + /** + * Matching facet values. + */ facetHits: FacetHits[]; /** diff --git a/packages/client-search/model/searchForFacetsOptions.ts b/packages/client-search/model/searchForFacetsOptions.ts index 68d26be39..d599af5dc 100644 --- a/packages/client-search/model/searchForFacetsOptions.ts +++ b/packages/client-search/model/searchForFacetsOptions.ts @@ -9,7 +9,7 @@ export type SearchForFacetsOptions = { facet: string; /** - * Algolia index name. + * Index name. */ indexName: string; @@ -19,7 +19,7 @@ export type SearchForFacetsOptions = { facetQuery?: string; /** - * Maximum number of facet hits to return when [searching for facet values](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#search-for-facet-values). + * 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; diff --git a/packages/client-search/model/searchForHitsOptions.ts b/packages/client-search/model/searchForHitsOptions.ts index f75300dbc..08edcf846 100644 --- a/packages/client-search/model/searchForHitsOptions.ts +++ b/packages/client-search/model/searchForHitsOptions.ts @@ -4,7 +4,7 @@ import type { SearchTypeDefault } from './searchTypeDefault'; export type SearchForHitsOptions = { /** - * Algolia index name. + * Index name. */ indexName: string; diff --git a/packages/client-search/model/searchHits.ts b/packages/client-search/model/searchHits.ts index 8826d69fb..13dafbaba 100644 --- a/packages/client-search/model/searchHits.ts +++ b/packages/client-search/model/searchHits.ts @@ -3,10 +3,13 @@ import type { Hit } from './hit'; export type SearchHits> = Record & { + /** + * Search results (hits). Hits are records from your index that match the search criteria, augmented with additional attributes, such as, for highlighting. + */ hits: Array>; /** - * Text to search for in an index. + * Search query. */ query: string; diff --git a/packages/client-search/model/searchParamsQuery.ts b/packages/client-search/model/searchParamsQuery.ts index 39058cbe1..9f1926f6c 100644 --- a/packages/client-search/model/searchParamsQuery.ts +++ b/packages/client-search/model/searchParamsQuery.ts @@ -2,7 +2,7 @@ export type SearchParamsQuery = { /** - * Text to search for in an index. + * Search query. */ query?: string; }; diff --git a/packages/client-search/model/searchRulesParams.ts b/packages/client-search/model/searchRulesParams.ts index 18ddeee87..f95752470 100644 --- a/packages/client-search/model/searchRulesParams.ts +++ b/packages/client-search/model/searchRulesParams.ts @@ -7,19 +7,19 @@ import type { Anchoring } from './anchoring'; */ export type SearchRulesParams = { /** - * Rule object query. + * Search query for rules. */ query?: string; anchoring?: Anchoring; /** - * Restricts responses to the specified [contextual rule](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/how-to/customize-search-results-by-platform/#creating-contextual-rules). + * Only return rules that match the context (exact match). */ context?: string; /** - * Requested page (the first page is page 0). + * Requested page of the API response. */ page?: number; @@ -29,12 +29,7 @@ export type SearchRulesParams = { hitsPerPage?: number; /** - * Restricts responses to enabled rules. When not specified (default), _all_ rules are retrieved. + * If `true`, return only enabled rules. If `false`, return only inactive rules. By default, _all_ rules are returned. */ enabled?: boolean | null; - - /** - * Request options to send with the API call. - */ - requestOptions?: Array>; }; diff --git a/packages/client-search/model/searchRulesResponse.ts b/packages/client-search/model/searchRulesResponse.ts index f16041975..ababfe4d8 100644 --- a/packages/client-search/model/searchRulesResponse.ts +++ b/packages/client-search/model/searchRulesResponse.ts @@ -4,12 +4,12 @@ import type { Rule } from './rule'; export type SearchRulesResponse = { /** - * Fetched rules. + * Rules that matched the search criteria. */ hits: Rule[]; /** - * Number of fetched rules. + * Number of rules that matched the search criteria. */ nbHits: number; diff --git a/packages/client-search/model/searchStrategy.ts b/packages/client-search/model/searchStrategy.ts index 84d4ae8be..1bda46977 100644 --- a/packages/client-search/model/searchStrategy.ts +++ b/packages/client-search/model/searchStrategy.ts @@ -1,6 +1,6 @@ // 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. /** - * - `none`: executes all queries. - `stopIfEnoughMatches`: executes queries one by one, stopping further query execution as soon as a query matches at least the `hitsPerPage` number of results. + * Strategy for multiple search queries: - `none`. Run all queries. - `stopIfEnoughMatches`. Run the queries one by one, stopping as soon as a query matches at least the `hitsPerPage` number of results. */ export type SearchStrategy = 'none' | 'stopIfEnoughMatches'; diff --git a/packages/client-search/model/searchSynonymsParams.ts b/packages/client-search/model/searchSynonymsParams.ts index 2e3596e25..aba75f43f 100644 --- a/packages/client-search/model/searchSynonymsParams.ts +++ b/packages/client-search/model/searchSynonymsParams.ts @@ -4,14 +4,14 @@ import type { SynonymType } from './synonymType'; export type SearchSynonymsParams = { /** - * Text to search for in an index. + * Search query. */ query?: string; type?: SynonymType; /** - * Page to retrieve (the first page is `0`, not `1`). + * Page of search results to retrieve. */ page?: number; diff --git a/packages/client-search/model/searchSynonymsResponse.ts b/packages/client-search/model/searchSynonymsResponse.ts index ac9e1a4a4..cef9b724f 100644 --- a/packages/client-search/model/searchSynonymsResponse.ts +++ b/packages/client-search/model/searchSynonymsResponse.ts @@ -4,12 +4,12 @@ import type { SynonymHit } from './synonymHit'; export type SearchSynonymsResponse = Record & { /** - * Synonym objects. + * Matching synonyms. */ hits: SynonymHit[]; /** - * Number of hits the search query matched. + * Number of results (hits). */ nbHits: number; }; diff --git a/packages/client-search/model/searchUserIdsParams.ts b/packages/client-search/model/searchUserIdsParams.ts index dab21cd14..b92f2a375 100644 --- a/packages/client-search/model/searchUserIdsParams.ts +++ b/packages/client-search/model/searchUserIdsParams.ts @@ -15,7 +15,7 @@ export type SearchUserIdsParams = { clusterName?: string; /** - * Page to retrieve (the first page is `0`, not `1`). + * Page of search results to retrieve. */ page?: number; diff --git a/packages/client-search/model/searchUserIdsResponse.ts b/packages/client-search/model/searchUserIdsResponse.ts index bf3191c56..6a6c1e143 100644 --- a/packages/client-search/model/searchUserIdsResponse.ts +++ b/packages/client-search/model/searchUserIdsResponse.ts @@ -12,12 +12,12 @@ export type SearchUserIdsResponse = { hits: UserHit[]; /** - * Number of hits the search query matched. + * Number of results (hits). */ nbHits: number; /** - * Page to retrieve (the first page is `0`, not `1`). + * Page of search results to retrieve. */ page: number; diff --git a/packages/client-search/model/securedAPIKeyRestrictions.ts b/packages/client-search/model/securedAPIKeyRestrictions.ts index bba07db28..c230dee7d 100644 --- a/packages/client-search/model/securedAPIKeyRestrictions.ts +++ b/packages/client-search/model/securedAPIKeyRestrictions.ts @@ -6,27 +6,27 @@ export type SecuredAPIKeyRestrictions = { searchParams?: SearchParamsObject; /** - * Filters that apply to every search made with the secured API key. You can add extra filters at search time with the filters query parameter. For example, if you set the filter group:admin on your generated API key, and you add groups:press OR groups:visitors with the filters query parameter, your final search filter is equivalent to groups:admin AND (groups:press OR groups:visitors). + * Filters that apply to every search made with the secured API key. Extra filters added at search time will be combined with `AND`. For example, if you set `group:admin` as fixed filter on your generated API key, and add `groups:visitors` to the search query, the complete set of filters will be `group:admin AND groups:visitors`. */ filters?: string; /** - * Unix timestamp used to set the expiration date of the API key. + * Timestamp in [Unix epoch time](https://en.wikipedia.org/wiki/Unix_time) when the API key should expire. */ validUntil?: number; /** - * Index names that can be queried. + * Index names or patterns that this API key can access. By default, an API key can access all indices in the same application. You can use leading and trailing wildcard characters (`*`): - `dev_*` matches all indices starting with \"dev_\". - `*_dev` matches all indices ending with \"_dev\". - `*_products_*` matches all indices containing \"_products_\". */ restrictIndices?: string[]; /** - * IPv4 network allowed to use the generated key. Use this to protect against API key leaking and reuse. You can only provide a single source, but you can specify a range of IPs (for example, 192.168.1.0/24). + * IP network that are allowed to use this key. You can only add a single source, but you can provide a range of IP addresses. Use this to protect against API key leaking and reuse. */ restrictSources?: string; /** - * Unique user IP address. This can be useful when you want to impose a rate limit on specific users. By default, rate limits are set based on the IP address. This can become an issue when several users search from the same IP address. To avoid this, you can set a unique userToken for each user when generating their API key. This lets you restrict each user to a maximum number of API calls per hour, even if they share their IP with another user. Specifying the userToken in a secured API key is also a good security practice as it ensures users don\'t change it. Many features like Analytics, Personalization, and Dynamic Re-ranking rely on the authenticity of user identifiers. Setting the userToken at the API key level ensures that downstream services work as expected and prevents abuse. + * Pseudonymous user identifier to restrict usage of this API key to specific users. By default, rate limits are set based on IP addresses. This can be an issue if many users search from the same IP address. To avoid this, add a user token to each generated API key. */ userToken?: string; }; diff --git a/packages/client-search/model/semanticSearch.ts b/packages/client-search/model/semanticSearch.ts index c9b832249..86cfd43a0 100644 --- a/packages/client-search/model/semanticSearch.ts +++ b/packages/client-search/model/semanticSearch.ts @@ -1,11 +1,11 @@ // 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. /** - * Settings for the semantic search part of NeuralSearch. Only used when `mode` is _neuralSearch_. + * Settings for the semantic search part of NeuralSearch. Only used when `mode` is `neuralSearch`. */ export type SemanticSearch = { /** - * Indices from which to collect click and conversion events. If null, the current index and replica group will be used as the event source. + * Indices from which to collect click and conversion events. If null, the current index and all its replicas are used. */ eventSources?: string[] | null; }; diff --git a/packages/client-search/model/snippetResultOption.ts b/packages/client-search/model/snippetResultOption.ts index cb21bd0f6..daab65f2d 100644 --- a/packages/client-search/model/snippetResultOption.ts +++ b/packages/client-search/model/snippetResultOption.ts @@ -3,11 +3,11 @@ import type { MatchLevel } from './matchLevel'; /** - * Snippeted attributes show parts of the matched attributes. Only returned when attributesToSnippet is non-empty. + * Snippets that show the context around a matching search query. */ export type SnippetResultOption = { /** - * Markup text with `facetQuery` matches highlighted. + * Highlighted attribute value, including HTML tags. */ value: string; diff --git a/packages/client-search/model/sortRemainingBy.ts b/packages/client-search/model/sortRemainingBy.ts index a5faf046e..7da7c289e 100644 --- a/packages/client-search/model/sortRemainingBy.ts +++ b/packages/client-search/model/sortRemainingBy.ts @@ -1,6 +1,6 @@ // 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. /** - * How to display the remaining items: - `count`: facet count (descending). - `alpha`: alphabetical (ascending). - `hidden`: show only pinned values. + * Order of facet values that aren\'t explicitly positioned with the `order` setting.
count
Order remaining facet values by decreasing count. The count is the number of matching records containing this facet value.
alpha
Sort facet values alphabetically.
hidden
Don\'t show facet values that aren\'t explicitly positioned.
. */ export type SortRemainingBy = 'alpha' | 'count' | 'hidden'; diff --git a/packages/client-search/model/tagFilters.ts b/packages/client-search/model/tagFilters.ts index 1b7e964bd..966082364 100644 --- a/packages/client-search/model/tagFilters.ts +++ b/packages/client-search/model/tagFilters.ts @@ -3,6 +3,6 @@ import type { MixedSearchFilters } from './mixedSearchFilters'; /** - * [Filter hits by tags](https://www.algolia.com/doc/api-reference/api-parameters/tagFilters/). + * Filter the search by values of the special `_tags` attribute. **Prefer using the `filters` parameter, which supports all filter types and combinations with boolean operators.** Different from regular facets, `_tags` can only be used for filtering (including or excluding records). You won\'t get a facet count. The same combination and escaping rules apply as for `facetFilters`. */ export type TagFilters = MixedSearchFilters[] | string; diff --git a/packages/client-search/model/taskStatus.ts b/packages/client-search/model/taskStatus.ts index 8f335ad21..169dd7bf2 100644 --- a/packages/client-search/model/taskStatus.ts +++ b/packages/client-search/model/taskStatus.ts @@ -1,6 +1,6 @@ // 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. /** - * _published_ if the task has been processed, _notPublished_ otherwise. + * Task status, `published` if the task is completed, `notPublished` otherwise. */ export type TaskStatus = 'notPublished' | 'published'; diff --git a/packages/client-search/model/timeRange.ts b/packages/client-search/model/timeRange.ts index cfd663c8a..dee6043c9 100644 --- a/packages/client-search/model/timeRange.ts +++ b/packages/client-search/model/timeRange.ts @@ -2,12 +2,12 @@ export type TimeRange = { /** - * Lower bound of the time range (Unix timestamp). + * When the rule should start to be active, in Unix epoch time. */ from: number; /** - * Upper bound of the time range (Unix timestamp). + * When the rule should stop to be active, in Unix epoch time. */ until: number; }; diff --git a/packages/client-search/model/typoTolerance.ts b/packages/client-search/model/typoTolerance.ts index 58ae716ef..0bd64036f 100644 --- a/packages/client-search/model/typoTolerance.ts +++ b/packages/client-search/model/typoTolerance.ts @@ -3,6 +3,6 @@ import type { TypoToleranceEnum } from './typoToleranceEnum'; /** - * Controls whether [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/) is enabled and how it is applied. + * Whether [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/) is enabled and how it is applied. If typo tolerance is true, `min`, or `strict`, [word splitting and concetenation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/splitting-and-concatenation/) is also active. */ export type TypoTolerance = TypoToleranceEnum | boolean; diff --git a/packages/client-search/model/typoToleranceEnum.ts b/packages/client-search/model/typoToleranceEnum.ts index 05cf7b62d..a33877b0d 100644 --- a/packages/client-search/model/typoToleranceEnum.ts +++ b/packages/client-search/model/typoToleranceEnum.ts @@ -1,3 +1,6 @@ // 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. +/** + * - `min`. Return matches with the lowest number of typos. For example, if you have matches without typos, only include those. But if there are no matches without typos (with 1 typo), include matches with 1 typo (2 typos). - `strict`. Return matches with the two lowest numbers of typos. With `strict`, the Typo ranking criterion is applied first in the `ranking` setting. + */ export type TypoToleranceEnum = 'min' | 'strict'; diff --git a/packages/client-search/model/updatedAtResponse.ts b/packages/client-search/model/updatedAtResponse.ts index 9f755ba7b..f36d93942 100644 --- a/packages/client-search/model/updatedAtResponse.ts +++ b/packages/client-search/model/updatedAtResponse.ts @@ -5,7 +5,7 @@ */ export type UpdatedAtResponse = { /** - * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the `task` operation and this `taskID`. + * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the [`task` operation](#tag/Indices/operation/getTask) and this `taskID`. */ taskID: number; diff --git a/packages/client-search/model/updatedAtWithObjectIdResponse.ts b/packages/client-search/model/updatedAtWithObjectIdResponse.ts index bda44f362..0c1bde66d 100644 --- a/packages/client-search/model/updatedAtWithObjectIdResponse.ts +++ b/packages/client-search/model/updatedAtWithObjectIdResponse.ts @@ -5,7 +5,7 @@ */ export type UpdatedAtWithObjectIdResponse = { /** - * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the `task` operation and this `taskID`. + * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the [`task` operation](#tag/Indices/operation/getTask) and this `taskID`. */ taskID?: number; @@ -15,7 +15,7 @@ export type UpdatedAtWithObjectIdResponse = { updatedAt?: string; /** - * Unique object identifier. + * Unique record identifier. */ objectID?: string; }; diff --git a/packages/client-search/model/updatedRuleResponse.ts b/packages/client-search/model/updatedRuleResponse.ts index 9e445c836..2a2b24689 100644 --- a/packages/client-search/model/updatedRuleResponse.ts +++ b/packages/client-search/model/updatedRuleResponse.ts @@ -2,7 +2,7 @@ export type UpdatedRuleResponse = { /** - * Unique object identifier. + * Unique identifier of a rule object. */ objectID: string; @@ -12,7 +12,7 @@ export type UpdatedRuleResponse = { updatedAt: string; /** - * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the `task` operation and this `taskID`. + * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the [`task` operation](#tag/Indices/operation/getTask) and this `taskID`. */ taskID: number; }; diff --git a/packages/client-search/model/userHit.ts b/packages/client-search/model/userHit.ts index 6a288e389..b8caa118a 100644 --- a/packages/client-search/model/userHit.ts +++ b/packages/client-search/model/userHit.ts @@ -4,7 +4,7 @@ import type { UserHighlightResult } from './userHighlightResult'; export type UserHit = { /** - * UserID of the user. + * User ID. */ userID: string; diff --git a/packages/client-search/model/userId.ts b/packages/client-search/model/userId.ts index 731250edc..e46823f8a 100644 --- a/packages/client-search/model/userId.ts +++ b/packages/client-search/model/userId.ts @@ -5,7 +5,7 @@ */ export type UserId = { /** - * UserID of the user. + * User ID. */ userID: string; diff --git a/packages/client-search/model/value.ts b/packages/client-search/model/value.ts index 9bbf488f6..9054c5e5d 100644 --- a/packages/client-search/model/value.ts +++ b/packages/client-search/model/value.ts @@ -4,7 +4,7 @@ import type { SortRemainingBy } from './sortRemainingBy'; export type Value = { /** - * Pinned order of facet lists. + * Explicit order of facets or facet values. This setting lets you always show specific facets or facet values at the top of the list. */ order?: string[]; diff --git a/packages/client-search/src/searchClient.ts b/packages/client-search/src/searchClient.ts index 0eac8bf7d..e1dcba8f3 100644 --- a/packages/client-search/src/searchClient.ts +++ b/packages/client-search/src/searchClient.ts @@ -106,6 +106,7 @@ import type { ReplaceSourceResponse } from '../model/replaceSourceResponse'; import type { Rule } from '../model/rule'; import type { SaveObjectResponse } from '../model/saveObjectResponse'; import type { SaveSynonymResponse } from '../model/saveSynonymResponse'; +import type { SearchDictionaryEntriesResponse } from '../model/searchDictionaryEntriesResponse'; import type { SearchForFacetValuesResponse } from '../model/searchForFacetValuesResponse'; import type { SearchMethodParams } from '../model/searchMethodParams'; import type { SearchResponse } from '../model/searchResponse'; @@ -592,7 +593,7 @@ export function createSearchClient({ return { copyOperationResponse, batchResponses, moveOperationResponse }; }, /** - * Add a new API key with specific permissions and restrictions. The request must be authenticated with the admin API key. The response returns an API key string. + * Creates a new API key with specific permissions and restrictions. * * Required API Key ACLs: * - admin. @@ -632,15 +633,15 @@ export function createSearchClient({ }, /** - * If you use an existing `objectID`, the existing record will be replaced with the new one. To update only some attributes of an existing record, use the [`partial` operation](#tag/Records/operation/partialUpdateObject) instead. To add multiple records to your index in a single API request, use the [`batch` operation](#tag/Records/operation/batch). + * If a record with the specified object ID exists, the existing record is replaced. Otherwise, a new record is added to the index. To update _some_ attributes of an existing record, use the [`partial` operation](#tag/Records/operation/partialUpdateObject) instead. To add, update, or replace multiple records, use the [`batch` operation](#tag/Records/operation/batch). * * Required API Key ACLs: * - addObject. * * @param addOrUpdateObject - The addOrUpdateObject object. - * @param addOrUpdateObject.indexName - Index on which to perform the request. - * @param addOrUpdateObject.objectID - Unique record (object) identifier. - * @param addOrUpdateObject.body - Algolia record. + * @param addOrUpdateObject.indexName - Name of the index on which to perform the operation. + * @param addOrUpdateObject.objectID - Unique record identifier. + * @param addOrUpdateObject.body - The record, a schemaless object with attributes that are useful in the context of search and discovery. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ addOrUpdateObject( @@ -683,7 +684,7 @@ export function createSearchClient({ }, /** - * Add a source to the list of allowed sources. + * Adds a source to the list of allowed sources. * * Required API Key ACLs: * - admin. @@ -723,13 +724,13 @@ export function createSearchClient({ }, /** - * Assign or move a user ID to a cluster. The time it takes to move a user is proportional to the amount of data linked to the user ID. + * Assigns or moves a user ID to a cluster. The time it takes to move a user is proportional to the amount of data linked to the user ID. * * Required API Key ACLs: * - admin. * * @param assignUserId - The assignUserId object. - * @param assignUserId.xAlgoliaUserID - UserID to assign. + * @param assignUserId.xAlgoliaUserID - User ID to assign. * @param assignUserId.assignUserIdParams - The assignUserIdParams object. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -775,10 +776,10 @@ export function createSearchClient({ }, /** - * To reduce the time spent on network round trips, you can perform several write actions in a single API call. Actions are applied in the order they are specified. The supported `action`s are equivalent to the individual operations of the same name. + * Adds, updates, or deletes records in one index with a single API request. Batching index updates reduces latency and increases data integrity. - Actions are applied in the order they\'re specified. - Actions are equivalent to the individual API requests of the same name. * * @param batch - The batch object. - * @param batch.indexName - Index on which to perform the request. + * @param batch.indexName - Name of the index on which to perform the operation. * @param batch.batchWriteParams - The batchWriteParams object. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -823,13 +824,13 @@ export function createSearchClient({ }, /** - * Assign multiple user IDs to a cluster. **You can\'t _move_ users with this operation.**. + * Assigns multiple user IDs to a cluster. **You can\'t move users with this operation**. * * Required API Key ACLs: * - admin. * * @param batchAssignUserIds - The batchAssignUserIds object. - * @param batchAssignUserIds.xAlgoliaUserID - UserID to assign. + * @param batchAssignUserIds.xAlgoliaUserID - User ID to assign. * @param batchAssignUserIds.batchAssignUserIdsParams - The batchAssignUserIdsParams object. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -880,13 +881,13 @@ export function createSearchClient({ }, /** - * Add or remove a batch of dictionary entries. + * Adds or deletes multiple entries from your plurals, segmentation, or stop word dictionaries. * * Required API Key ACLs: * - editSettings. * * @param batchDictionaryEntries - The batchDictionaryEntries object. - * @param batchDictionaryEntries.dictionaryName - Dictionary to search in. + * @param batchDictionaryEntries.dictionaryName - Dictionary type in which to search. * @param batchDictionaryEntries.batchDictionaryEntriesParams - The batchDictionaryEntriesParams object. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -934,13 +935,13 @@ export function createSearchClient({ }, /** - * Retrieve up to 1,000 records per call. Supports full-text search and filters. For better performance, it doesn\'t support: - The `distinct` query parameter - Sorting by typos, proximity, words, or geographical distance. + * Retrieves records from an index, up to 1,000 per request. While searching retrieves _hits_ (records augmented with attributes for highlighting and ranking details), browsing _just_ returns matching records. This can be useful if you want to export your indices. - The Analytics API doesn\'t collect data when using `browse`. - Records are ranked by attributes and custom ranking. - Deduplication (`distinct`) is turned off. - There\'s no ranking for: typo-tolerance, number of matched words, proximity, geo distance. * * Required API Key ACLs: * - browse. * * @param browse - The browse object. - * @param browse.indexName - Index on which to perform the request. + * @param browse.indexName - Name of the index on which to perform the operation. * @param browse.browseParams - The browseParams object. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -973,13 +974,13 @@ export function createSearchClient({ }, /** - * Delete the records but leave settings and index-specific API keys untouched. + * Deletes only the records from an index while keeping settings, synonyms, and rules. * * Required API Key ACLs: * - deleteIndex. * * @param clearObjects - The clearObjects object. - * @param clearObjects.indexName - Index on which to perform the request. + * @param clearObjects.indexName - Name of the index on which to perform the operation. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ clearObjects( @@ -1010,14 +1011,14 @@ export function createSearchClient({ }, /** - * Delete all rules in the index. + * Deletes all rules from the index. * * Required API Key ACLs: * - editSettings. * * @param clearRules - The clearRules object. - * @param clearRules.indexName - Index on which to perform the request. - * @param clearRules.forwardToReplicas - Indicates whether changed index settings are forwarded to the replica indices. + * @param clearRules.indexName - Name of the index on which to perform the operation. + * @param clearRules.forwardToReplicas - Whether changes are applied to replica indices. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ clearRules( @@ -1052,14 +1053,14 @@ export function createSearchClient({ }, /** - * Delete all synonyms in the index. + * Deletes all synonyms from the index. * * Required API Key ACLs: * - editSettings. * * @param clearSynonyms - The clearSynonyms object. - * @param clearSynonyms.indexName - Index on which to perform the request. - * @param clearSynonyms.forwardToReplicas - Indicates whether changed index settings are forwarded to the replica indices. + * @param clearSynonyms.indexName - Name of the index on which to perform the operation. + * @param clearSynonyms.forwardToReplicas - Whether changes are applied to replica indices. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ clearSynonyms( @@ -1226,7 +1227,7 @@ export function createSearchClient({ }, /** - * Delete an existing API key. The request must be authenticated with the admin API key. + * Deletes the API key. * * Required API Key ACLs: * - admin. @@ -1263,13 +1264,13 @@ export function createSearchClient({ }, /** - * This operation doesn\'t support all the query options, only its filters (numeric, facet, or tag) and geo queries. It doesn\'t accept empty filters or queries. + * This operation doesn\'t accept empty queries or filters. It\'s more efficient to get a list of object IDs with the [`browse` operation](#tag/Search/operation/browse), and then delete the records using the [`batch` operation](tag/Records/operation/batch). * * Required API Key ACLs: * - deleteIndex. * * @param deleteBy - The deleteBy object. - * @param deleteBy.indexName - Index on which to perform the request. + * @param deleteBy.indexName - Name of the index on which to perform the operation. * @param deleteBy.deleteByParams - The deleteByParams object. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -1308,13 +1309,13 @@ export function createSearchClient({ }, /** - * Delete an existing index. + * Deletes an index and all its settings. - Deleting an index doesn\'t delete its analytics data. - If you try to delete a non-existing index, the operation is ignored without warning. - If the index you want to delete has replica indices, the replicas become independent indices. - If the index you want to delete is a replica index, you must first unlink it from its primary index before you can delete it. For more information, see [Delete replica indices](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/how-to/deleting-replicas/). * * Required API Key ACLs: * - deleteIndex. * * @param deleteIndex - The deleteIndex object. - * @param deleteIndex.indexName - Index on which to perform the request. + * @param deleteIndex.indexName - Name of the index on which to perform the operation. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ deleteIndex( @@ -1345,14 +1346,14 @@ export function createSearchClient({ }, /** - * To delete a set of records matching a query, use the [`deleteByQuery` operation](#tag/Records/operation/deleteBy) instead. + * Deletes a record by its object ID. To delete more than one record, use the [`batch` operation](#tag/Records/operation/batch). To delete records matching a query, use the [`deleteByQuery` operation](#tag/Records/operation/deleteBy). * * Required API Key ACLs: * - deleteObject. * * @param deleteObject - The deleteObject object. - * @param deleteObject.indexName - Index on which to perform the request. - * @param deleteObject.objectID - Unique record (object) identifier. + * @param deleteObject.indexName - Name of the index on which to perform the operation. + * @param deleteObject.objectID - Unique record identifier. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ deleteObject( @@ -1388,15 +1389,15 @@ export function createSearchClient({ }, /** - * Delete a rule by its `objectID`. To find the `objectID` for rules, use the [`search` operation](#tag/Rules/operation/searchRules). + * Deletes a rule by its ID. To find the object ID for rules, use the [`search` operation](#tag/Rules/operation/searchRules). * * Required API Key ACLs: * - editSettings. * * @param deleteRule - The deleteRule object. - * @param deleteRule.indexName - Index on which to perform the request. + * @param deleteRule.indexName - Name of the index on which to perform the operation. * @param deleteRule.objectID - Unique identifier of a rule object. - * @param deleteRule.forwardToReplicas - Indicates whether changed index settings are forwarded to the replica indices. + * @param deleteRule.forwardToReplicas - Whether changes are applied to replica indices. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ deleteRule( @@ -1436,7 +1437,7 @@ export function createSearchClient({ }, /** - * Remove a source from the list of allowed sources. + * Deletes a source from the list of allowed sources. * * Required API Key ACLs: * - admin. @@ -1473,15 +1474,15 @@ export function createSearchClient({ }, /** - * Delete a synonym by its `objectID`. To find the object IDs of your synonyms, use the [`search` operation](#tag/Synonyms/operation/searchSynonyms). + * Deletes a synonym by its ID. To find the object IDs of your synonyms, use the [`search` operation](#tag/Synonyms/operation/searchSynonyms). * * Required API Key ACLs: * - editSettings. * * @param deleteSynonym - The deleteSynonym object. - * @param deleteSynonym.indexName - Index on which to perform the request. + * @param deleteSynonym.indexName - Name of the index on which to perform the operation. * @param deleteSynonym.objectID - Unique identifier of a synonym object. - * @param deleteSynonym.forwardToReplicas - Indicates whether changed index settings are forwarded to the replica indices. + * @param deleteSynonym.forwardToReplicas - Whether changes are applied to replica indices. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ deleteSynonym( @@ -1521,7 +1522,7 @@ export function createSearchClient({ }, /** - * Get the permissions and restrictions of a specific API key. When authenticating with the admin API key, you can request information for any of your application\'s keys. When authenticating with other API keys, you can only retrieve information for that key. + * Gets the permissions and restrictions of an API key. When authenticating with the admin API key, you can request information for any of your application\'s keys. When authenticating with other API keys, you can only retrieve information for that key. * * @param getApiKey - The getApiKey object. * @param getApiKey.key - API key. @@ -1555,7 +1556,7 @@ export function createSearchClient({ }, /** - * Lists Algolia\'s [supported languages](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages/) and any customizations applied to each language\'s [stop word](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/how-to/customize-stop-words/), [plural](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/how-to/customize-plurals-and-other-declensions/), and [segmentation (compound)](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/how-to/customize-segmentation/) features. + * Lists supported languages with their supported dictionary types and number of custom entries. * * Required API Key ACLs: * - settings. @@ -1580,7 +1581,7 @@ export function createSearchClient({ }, /** - * Get the languages for which [stop words are turned off](#tag/Dictionaries/operation/setDictionarySettings). + * Retrieves the languages for which standard dictionary entries are turned off. * * Required API Key ACLs: * - settings. @@ -1605,16 +1606,16 @@ export function createSearchClient({ }, /** - * The request must be authenticated by an API key with the [`logs` ACL](https://www.algolia.com/doc/guides/security/api-keys/#access-control-list-acl). Logs are held for the last seven days. There\'s also a logging limit of 1,000 API calls per server. This request counts towards your [operations quota](https://support.algolia.com/hc/en-us/articles/4406981829777-How-does-Algolia-count-records-and-operations-) but doesn\'t appear in the logs itself. > **Note**: To fetch the logs for a Distributed Search Network (DSN) cluster, target the [DSN\'s endpoint](https://www.algolia.com/doc/guides/scaling/distributed-search-network-dsn/#accessing-dsn-servers). + * The request must be authenticated by an API key with the [`logs` ACL](https://www.algolia.com/doc/guides/security/api-keys/#access-control-list-acl). - Logs are held for the last seven days. - Up to 1,000 API requests per server are logged. - This request counts towards your [operations quota](https://support.algolia.com/hc/en-us/articles/4406981829777-How-does-Algolia-count-records-and-operations-) but doesn\'t appear in the logs itself. * * Required API Key ACLs: * - logs. * * @param getLogs - The getLogs object. - * @param getLogs.offset - First log entry to retrieve. Sorted by decreasing date with 0 being the most recent. + * @param getLogs.offset - First log entry to retrieve. The most recent entries are listed first. * @param getLogs.length - Maximum number of entries to retrieve. - * @param getLogs.indexName - Index for which log entries should be retrieved. When omitted, log entries are retrieved for all indices. - * @param getLogs.type - Type of log entries to retrieve. When omitted, all log entries are retrieved. + * @param getLogs.indexName - Index for which to retrieve log entries. By default, log entries are retrieved for all indices. + * @param getLogs.type - Type of log entries to retrieve. By default, all log entries are retrieved. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ getLogs( @@ -1652,15 +1653,15 @@ export function createSearchClient({ }, /** - * To get more than one record, use the [`objects` operation](#tag/Records/operation/getObjects). + * Retrieves one record by its object ID. To retrieve more than one record, use the [`objects` operation](#tag/Records/operation/getObjects). * * Required API Key ACLs: * - search. * * @param getObject - The getObject object. - * @param getObject.indexName - Index on which to perform the request. - * @param getObject.objectID - Unique record (object) identifier. - * @param getObject.attributesToRetrieve - Attributes to include with the records in the response. This is useful to reduce the size of the API response. By default, all retrievable attributes are returned. `objectID` is always retrieved, even when not specified. [`unretrievableAttributes`](https://www.algolia.com/doc/api-reference/api-parameters/unretrievableAttributes/) won\'t be retrieved unless the request is authenticated with the admin API key. + * @param getObject.indexName - Name of the index on which to perform the operation. + * @param getObject.objectID - Unique record identifier. + * @param getObject.attributesToRetrieve - Attributes to include with the records in the response. This is useful to reduce the size of the API response. By default, all retrievable attributes are returned. `objectID` is always retrieved. Attributes included in `unretrievableAttributes` won\'t be retrieved unless the request is authenticated with the admin API key. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ getObject( @@ -1700,7 +1701,7 @@ export function createSearchClient({ }, /** - * Retrieve one or more records, potentially from different indices, in a single API operation. Results will be received in the same order as the requests. + * Retrieves one or more records, potentially from different indices. Records are returned in the same order as the requests. * * Required API Key ACLs: * - search. @@ -1742,13 +1743,13 @@ export function createSearchClient({ }, /** - * Get a rule by its `objectID`. To find the `objectID` for rules, use the [`search` operation](#tag/Rules/operation/searchRules). + * Retrieves a rule by its ID. To find the object ID of rules, use the [`search` operation](#tag/Rules/operation/searchRules). * * Required API Key ACLs: * - settings. * * @param getRule - The getRule object. - * @param getRule.indexName - Index on which to perform the request. + * @param getRule.indexName - Name of the index on which to perform the operation. * @param getRule.objectID - Unique identifier of a rule object. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -1785,13 +1786,13 @@ export function createSearchClient({ }, /** - * Return an object containing an index\'s [configuration settings](https://www.algolia.com/doc/api-reference/settings-api-parameters/). + * Retrieves an object with non-null index settings. * * Required API Key ACLs: * - search. * * @param getSettings - The getSettings object. - * @param getSettings.indexName - Index on which to perform the request. + * @param getSettings.indexName - Name of the index on which to perform the operation. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ getSettings( @@ -1822,7 +1823,7 @@ export function createSearchClient({ }, /** - * Get all allowed sources (IP addresses). + * Retrieves all allowed IP addresses with access to your application. * * Required API Key ACLs: * - admin. @@ -1845,13 +1846,13 @@ export function createSearchClient({ }, /** - * Get a syonym by its `objectID`. To find the object IDs for your synonyms, use the [`search` operation](#tag/Synonyms/operation/searchSynonyms). + * Retrieves a syonym by its ID. To find the object IDs for your synonyms, use the [`search` operation](#tag/Synonyms/operation/searchSynonyms). * * Required API Key ACLs: * - settings. * * @param getSynonym - The getSynonym object. - * @param getSynonym.indexName - Index on which to perform the request. + * @param getSynonym.indexName - Name of the index on which to perform the operation. * @param getSynonym.objectID - Unique identifier of a synonym object. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -1888,13 +1889,13 @@ export function createSearchClient({ }, /** - * Some operations, such as copying an index, will respond with a `taskID` value. Use this value here to check the status of that task. + * Checks the status of a given task. Indexing tasks are asynchronous. When you add, update, or delete records or indices, a task is created on a queue and completed depending on the load on the server. The indexing tasks\' responses include a task ID that you can use to check the status. * * Required API Key ACLs: * - addObject. * * @param getTask - The getTask object. - * @param getTask.indexName - Index on which to perform the request. + * @param getTask.indexName - Name of the index on which to perform the operation. * @param getTask.taskID - Unique task identifier. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -1931,7 +1932,7 @@ export function createSearchClient({ }, /** - * Get the IDs of the 10 users with the highest number of records per cluster. Since it can take up to a few seconds to get the data from the different clusters, the response isn\'t real-time. + * Get the IDs of the 10 users with the highest number of records per cluster. Since it can take a few seconds to get the data from the different clusters, the response isn\'t real-time. * * Required API Key ACLs: * - admin. @@ -1956,13 +1957,13 @@ export function createSearchClient({ }, /** - * Returns the userID data stored in the mapping. Since it can take up to a few seconds to get the data from the different clusters, the response isn\'t real-time. + * Returns the user ID data stored in the mapping. Since it can take a few seconds to get the data from the different clusters, the response isn\'t real-time. * * Required API Key ACLs: * - admin. * * @param getUserId - The getUserId object. - * @param getUserId.userID - UserID to assign. + * @param getUserId.userID - User ID to assign. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ getUserId( @@ -1999,7 +2000,7 @@ export function createSearchClient({ * - admin. * * @param hasPendingMappings - The hasPendingMappings object. - * @param hasPendingMappings.getClusters - Indicates whether to include the cluster\'s pending mapping state in the response. + * @param hasPendingMappings.getClusters - Whether to include the cluster\'s pending mapping state in the response. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ hasPendingMappings( @@ -2025,7 +2026,7 @@ export function createSearchClient({ }, /** - * List all API keys associated with your Algolia application, including their permissions and restrictions. + * Lists all API keys associated with your Algolia application, including their permissions and restrictions. * * Required API Key ACLs: * - admin. @@ -2048,7 +2049,7 @@ export function createSearchClient({ }, /** - * List the available clusters in a multi-cluster setup. + * Lists the available clusters in a multi-cluster setup. * * Required API Key ACLs: * - admin. @@ -2073,14 +2074,14 @@ export function createSearchClient({ }, /** - * List indices in an Algolia application. + * Lists all indices in the current Algolia application. The request follows any index restrictions of the API key you use to make the request. * * Required API Key ACLs: * - listIndexes. * * @param listIndices - The listIndices object. - * @param listIndices.page - Returns the requested page number. The page size is determined by the `hitsPerPage` parameter. You can see the number of available pages in the `nbPages` response attribute. When `page` is null, the API response is not paginated. - * @param listIndices.hitsPerPage - Maximum number of hits per page. + * @param listIndices.page - Requested page of the API response. If `null`, the API response is not paginated. + * @param listIndices.hitsPerPage - Number of hits per page. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ listIndices( @@ -2110,14 +2111,14 @@ export function createSearchClient({ }, /** - * List the userIDs assigned to a multi-cluster application. Since it can take up to a few seconds to get the data from the different clusters, the response isn\'t real-time. + * Lists the userIDs assigned to a multi-cluster application. Since it can take a few seconds to get the data from the different clusters, the response isn\'t real-time. * * Required API Key ACLs: * - admin. * * @param listUserIds - The listUserIds object. - * @param listUserIds.page - Returns the requested page number. The page size is determined by the `hitsPerPage` parameter. You can see the number of available pages in the `nbPages` response attribute. When `page` is null, the API response is not paginated. - * @param listUserIds.hitsPerPage - Maximum number of hits per page. + * @param listUserIds.page - Requested page of the API response. If `null`, the API response is not paginated. + * @param listUserIds.hitsPerPage - Number of hits per page. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ listUserIds( @@ -2147,7 +2148,7 @@ export function createSearchClient({ }, /** - * To reduce the time spent on network round trips, you can perform several write actions in a single request. It\'s a multi-index version of the [`batch` operation](#tag/Records/operation/batch). Actions are applied in the order they are specified. The supported actions are equivalent to the individual operations of the same name. + * Adds, updates, or deletes records in multiple indices with a single API request. - Actions are applied in the order they are specified. - Actions are equivalent to the individual API requests of the same name. * * @param batchParams - The batchParams object. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. @@ -2184,13 +2185,13 @@ export function createSearchClient({ }, /** - * This `operation`, _copy_ or _move_, will copy or move a source index\'s (`IndexName`) records, settings, synonyms, and rules to a `destination` index. If the destination index exists, it will be replaced, except for index-specific API keys and analytics data. If the destination index doesn\'t exist, it will be created. The choice between moving or copying an index depends on your needs. Choose: - **Move** to rename an index. - **Copy** to create a new index with the same records and configuration as an existing one. > **Note**: When considering copying or moving, be aware of the [rate limitations](https://www.algolia.com/doc/guides/scaling/algolia-service-limits/#application-record-and-index-limits) on these processes and the [impact on your analytics data](https://www.algolia.com/doc/guides/sending-and-managing-data/manage-indices-and-apps/manage-indices/concepts/indices-analytics/). + * Copies or moves (renames) an index within the same Algolia application. - Existing destination indices are overwritten, except for index-specific API keys and analytics data. - If the destination index doesn\'t exist yet, it\'ll be created. **Copy** - Copying a source index that doesn\'t exist creates a new index with 0 records and default settings. - The API keys of the source index are merged with the existing keys in the destination index. - You can\'t copy the `enableReRanking`, `mode`, and `replicas` settings. - You can\'t copy to a destination index that already has replicas. - Be aware of the [size limits](https://www.algolia.com/doc/guides/scaling/algolia-service-limits/#application-record-and-index-limits). - Related guide: [Copy indices](https://www.algolia.com/doc/guides/sending-and-managing-data/manage-indices-and-apps/manage-indices/how-to/copy-indices/) **Move** - Moving a source index that doesn\'t exist is ignored without returning an error. - When moving an index, the analytics data keep their original name and a new set of analytics data is started for the new name. To access the original analytics in the dashboard, create an index with the original name. - If the destination index has replicas, moving will overwrite the existing index and copy the data to the replica indices. - Related guide: [Move indices](https://www.algolia.com/doc/guides/sending-and-managing-data/manage-indices-and-apps/manage-indices/how-to/move-indices/). * * Required API Key ACLs: * - addObject. * * @param operationIndex - The operationIndex object. - * @param operationIndex.indexName - Index on which to perform the request. + * @param operationIndex.indexName - Name of the index on which to perform the operation. * @param operationIndex.operationIndexParams - The operationIndexParams object. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -2240,16 +2241,16 @@ export function createSearchClient({ }, /** - * Add new attributes or update current ones in an existing record. You can use any first-level attribute but not nested attributes. If you specify a [nested attribute](https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/how-to/creating-and-using-nested-attributes/), the engine treats it as a replacement for its first-level ancestor. + * Adds new attributes to a record, or update existing ones. - If a record with the specified object ID doesn\'t exist, a new record is added to the index **if** `createIfNotExists` is true. - If the index doesn\'t exist yet, this method creates a new index. - You can use any first-level attribute but not nested attributes. If you specify a nested attribute, the engine treats it as a replacement for its first-level ancestor. * * Required API Key ACLs: * - addObject. * * @param partialUpdateObject - The partialUpdateObject object. - * @param partialUpdateObject.indexName - Index on which to perform the request. - * @param partialUpdateObject.objectID - Unique record (object) identifier. - * @param partialUpdateObject.attributesToUpdate - Object with attributes to update. - * @param partialUpdateObject.createIfNotExists - Indicates whether to create a new record if it doesn\'t exist yet. + * @param partialUpdateObject.indexName - Name of the index on which to perform the operation. + * @param partialUpdateObject.objectID - Unique record identifier. + * @param partialUpdateObject.attributesToUpdate - Attributes with their values. + * @param partialUpdateObject.createIfNotExists - Whether to create a new record if it doesn\'t exist. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ partialUpdateObject( @@ -2301,13 +2302,13 @@ export function createSearchClient({ }, /** - * Remove a userID and its associated data from the multi-clusters. + * Deletes a user ID and its associated data from the clusters. * * Required API Key ACLs: * - admin. * * @param removeUserId - The removeUserId object. - * @param removeUserId.userID - UserID to assign. + * @param removeUserId.userID - User ID to assign. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ removeUserId( @@ -2338,7 +2339,7 @@ export function createSearchClient({ }, /** - * Replace all allowed sources. + * Replaces the list of allowed sources. * * Required API Key ACLs: * - admin. @@ -2373,7 +2374,7 @@ export function createSearchClient({ }, /** - * Restore a deleted API key, along with its associated permissions. The request must be authenticated with the admin API key. + * Restores a deleted API key. Restoring resets the `validity` attribute to `0`. Algolia stores up to 1,000 API keys per application. If you create more, the oldest API keys are deleted and can\'t be restored. * * Required API Key ACLs: * - admin. @@ -2410,14 +2411,14 @@ export function createSearchClient({ }, /** - * Add a record (object) to an index or replace it. If the record doesn\'t contain an `objectID`, Algolia automatically adds it. If you use an existing `objectID`, the existing record is replaced with the new one. To add multiple records to your index in a single API request, use the [`batch` operation](#tag/Records/operation/batch). + * Adds a record to an index or replace it. - If the record doesn\'t have an object ID, a new record with an auto-generated object ID is added to your index. - If a record with the specified object ID exists, the existing record is replaced. - If a record with the specified object ID doesn\'t exist, a new record is added to your index. - If you add a record to an index that doesn\'t exist yet, a new index is created. To update _some_ attributes of a record, use the [`partial` operation](#tag/Records/operation/partial). To add, update, or replace multiple records, use the [`batch` operation](#tag/Records/operation/batch). * * Required API Key ACLs: * - addObject. * * @param saveObject - The saveObject object. - * @param saveObject.indexName - Index on which to perform the request. - * @param saveObject.body - The Algolia record. + * @param saveObject.indexName - Name of the index on which to perform the operation. + * @param saveObject.body - The record, a schemaless object with attributes that are useful in the context of search and discovery. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ saveObject( @@ -2455,16 +2456,16 @@ export function createSearchClient({ }, /** - * To create or update more than one rule, use the [`batch` operation](#tag/Rules/operation/saveRules). + * If a rule with the specified object ID doesn\'t exist, it\'s created. Otherwise, the existing rule is replaced. To create or update more than one rule, use the [`batch` operation](#tag/Rules/operation/saveRules). * * Required API Key ACLs: * - editSettings. * * @param saveRule - The saveRule object. - * @param saveRule.indexName - Index on which to perform the request. + * @param saveRule.indexName - Name of the index on which to perform the operation. * @param saveRule.objectID - Unique identifier of a rule object. * @param saveRule.rule - The rule object. - * @param saveRule.forwardToReplicas - Indicates whether changed index settings are forwarded to the replica indices. + * @param saveRule.forwardToReplicas - Whether changes are applied to replica indices. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ saveRule( @@ -2517,16 +2518,16 @@ export function createSearchClient({ }, /** - * Create or update multiple rules. + * Create or update multiple rules. If a rule with the specified object ID doesn\'t exist, Algolia creates a new one. Otherwise, existing rules are replaced. * * Required API Key ACLs: * - editSettings. * * @param saveRules - The saveRules object. - * @param saveRules.indexName - Index on which to perform the request. + * @param saveRules.indexName - Name of the index on which to perform the operation. * @param saveRules.rules - The rules object. - * @param saveRules.forwardToReplicas - Indicates whether changed index settings are forwarded to the replica indices. - * @param saveRules.clearExistingRules - Indicates whether existing rules should be deleted before adding this batch. + * @param saveRules.forwardToReplicas - Whether changes are applied to replica indices. + * @param saveRules.clearExistingRules - Whether existing rules should be deleted before adding this batch. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ saveRules( @@ -2577,16 +2578,16 @@ export function createSearchClient({ }, /** - * Add a [synonym](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/adding-synonyms/#the-different-types-of-synonyms) to an index or replace it. If the synonym `objectID` doesn\'t exist, Algolia adds a new one. If you use an existing synonym `objectID`, the existing synonym is replaced with the new one. To add multiple synonyms in a single API request, use the [`batch` operation](#tag/Synonyms/operation/saveSynonyms). + * If a synonym with the specified object ID doesn\'t exist, Algolia adds a new one. Otherwise, the existing synonym is replaced. To add multiple synonyms in a single API request, use the [`batch` operation](#tag/Synonyms/operation/saveSynonyms). * * Required API Key ACLs: * - editSettings. * * @param saveSynonym - The saveSynonym object. - * @param saveSynonym.indexName - Index on which to perform the request. + * @param saveSynonym.indexName - Name of the index on which to perform the operation. * @param saveSynonym.objectID - Unique identifier of a synonym object. * @param saveSynonym.synonymHit - The synonymHit object. - * @param saveSynonym.forwardToReplicas - Indicates whether changed index settings are forwarded to the replica indices. + * @param saveSynonym.forwardToReplicas - Whether changes are applied to replica indices. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ saveSynonym( @@ -2644,16 +2645,16 @@ export function createSearchClient({ }, /** - * Create or update multiple synonyms. + * If a synonym with the `objectID` doesn\'t exist, Algolia adds a new one. Otherwise, existing synonyms are replaced. * * Required API Key ACLs: * - editSettings. * * @param saveSynonyms - The saveSynonyms object. - * @param saveSynonyms.indexName - Index on which to perform the request. + * @param saveSynonyms.indexName - Name of the index on which to perform the operation. * @param saveSynonyms.synonymHit - The synonymHit object. - * @param saveSynonyms.forwardToReplicas - Indicates whether changed index settings are forwarded to the replica indices. - * @param saveSynonyms.replaceExistingSynonyms - Indicates whether to replace all synonyms in the index with the ones sent with this request. + * @param saveSynonyms.forwardToReplicas - Whether changes are applied to replica indices. + * @param saveSynonyms.replaceExistingSynonyms - Whether to replace all synonyms in the index with the ones sent with this request. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ saveSynonyms( @@ -2705,12 +2706,12 @@ export function createSearchClient({ }, /** - * Send multiple search queries to one or more indices. + * Sends multiple search request to one or more indices. This can be useful in these cases: - Different indices for different purposes, such as, one index for products, another one for marketing content. - Multiple searches to the same index—for example, with different filters. * * Required API Key ACLs: * - search. * - * @param searchMethodParams - Query requests and strategies. Results will be received in the same order as the queries. + * @param searchMethodParams - Muli-search request body. Results are returned in the same order as the requests. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ search( @@ -2772,13 +2773,13 @@ export function createSearchClient({ }, /** - * Search for standard and [custom](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/how-to/customize-stop-words/) entries in the [stop words](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/how-to/customize-stop-words/), [plurals](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/how-to/customize-plurals-and-other-declensions/), or [segmentation (compounds)](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/how-to/customize-segmentation/) dictionaries. + * Searches for standard and custom dictionary entries. * * Required API Key ACLs: * - settings. * * @param searchDictionaryEntries - The searchDictionaryEntries object. - * @param searchDictionaryEntries.dictionaryName - Dictionary to search in. + * @param searchDictionaryEntries.dictionaryName - Dictionary type in which to search. * @param searchDictionaryEntries.searchDictionaryEntriesParams - The searchDictionaryEntriesParams object. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -2788,7 +2789,7 @@ export function createSearchClient({ searchDictionaryEntriesParams, }: SearchDictionaryEntriesProps, requestOptions?: RequestOptions - ): Promise { + ): Promise { if (!dictionaryName) { throw new Error( 'Parameter `dictionaryName` is required when calling `searchDictionaryEntries`.' @@ -2828,14 +2829,14 @@ export function createSearchClient({ }, /** - * [Search for a facet\'s values](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#search-for-facet-values), optionally restricting the returned values to those contained in records matching other search criteria. > **Note**: Pagination isn\'t supported (`page` and `hitsPerPage` are ignored). By default, the engine returns a maximum of 10 values but you can adjust this with `maxFacetHits`. + * Searches for values of a specified facet attribute. - By default, facet values are sorted by decreasing count. You can adjust this with the `sortFacetValueBy` parameter. - Searching for facet values doesn\'t work if you have **more than 65 searchable facets and searchable attributes combined**. * * Required API Key ACLs: * - search. * * @param searchForFacetValues - The searchForFacetValues object. - * @param searchForFacetValues.indexName - Index on which to perform the request. - * @param searchForFacetValues.facetName - Facet name. + * @param searchForFacetValues.indexName - Name of the index on which to perform the operation. + * @param searchForFacetValues.facetName - Facet attribute in which to search for values. This attribute must be included in the `attributesForFaceting` index setting with the `searchable()` modifier. * @param searchForFacetValues.searchForFacetValuesRequest - The searchForFacetValuesRequest object. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -2879,13 +2880,13 @@ export function createSearchClient({ }, /** - * Search for rules in your index. You can control the search with parameters. To list all rules, send an empty request body. + * Searches for rules in your index. * * Required API Key ACLs: * - settings. * * @param searchRules - The searchRules object. - * @param searchRules.indexName - Index on which to perform the request. + * @param searchRules.indexName - Name of the index on which to perform the operation. * @param searchRules.searchRulesParams - The searchRulesParams object. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -2920,13 +2921,13 @@ export function createSearchClient({ }, /** - * Return records that match the query. + * Searches a single index and return matching search results (_hits_). This method lets you retrieve up to 1,000 hits. If you need more, use the [`browse` operation](#tag/Search/operation/browse) or increase the `paginatedLimitedTo` index setting. * * Required API Key ACLs: * - search. * * @param searchSingleIndex - The searchSingleIndex object. - * @param searchSingleIndex.indexName - Index on which to perform the request. + * @param searchSingleIndex.indexName - Name of the index on which to perform the operation. * @param searchSingleIndex.searchParams - The searchParams object. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -2961,13 +2962,13 @@ export function createSearchClient({ }, /** - * Search for synonyms in your index. You can control and filter the search with parameters. To get all synonyms, send an empty request body. + * Searches for synonyms in your index. * * Required API Key ACLs: * - settings. * * @param searchSynonyms - The searchSynonyms object. - * @param searchSynonyms.indexName - Index on which to perform the request. + * @param searchSynonyms.indexName - Name of the index on which to perform the operation. * @param searchSynonyms.searchSynonymsParams - Body of the `searchSynonyms` operation. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ @@ -3002,7 +3003,7 @@ export function createSearchClient({ }, /** - * Since it can take up to a few seconds to get the data from the different clusters, the response isn\'t real-time. To ensure rapid updates, the user IDs index isn\'t built at the same time as the mapping. Instead, it\'s built every 12 hours, at the same time as the update of user ID usage. For example, if you add or move a user ID, the search will show an old value until the next time the mapping is rebuilt (every 12 hours). + * Since it can take a few seconds to get the data from the different clusters, the response isn\'t real-time. To ensure rapid updates, the user IDs index isn\'t built at the same time as the mapping. Instead, it\'s built every 12 hours, at the same time as the update of user ID usage. For example, if you add or move a user ID, the search will show an old value until the next time the mapping is rebuilt (every 12 hours). * * Required API Key ACLs: * - admin. @@ -3044,7 +3045,7 @@ export function createSearchClient({ }, /** - * Set stop word settings for a specific language. + * Turns standard stop word dictionary entries on or off for a given language. * * Required API Key ACLs: * - editSettings. @@ -3084,15 +3085,15 @@ export function createSearchClient({ }, /** - * Update the specified [index settings](https://www.algolia.com/doc/api-reference/settings-api-parameters/). Specifying null for a setting resets it to its default value. + * Update the specified index settings. Index settings that you don\'t specify are left unchanged. Specify `null` to reset a setting to its default value. For best performance, update the index settings before you add new records to your index. * * Required API Key ACLs: * - editSettings. * * @param setSettings - The setSettings object. - * @param setSettings.indexName - Index on which to perform the request. + * @param setSettings.indexName - Name of the index on which to perform the operation. * @param setSettings.indexSettings - The indexSettings object. - * @param setSettings.forwardToReplicas - Indicates whether changed index settings are forwarded to the replica indices. + * @param setSettings.forwardToReplicas - Whether changes are applied to replica indices. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ setSettings( @@ -3134,7 +3135,7 @@ export function createSearchClient({ }, /** - * Replace the permissions of an existing API key. Any unspecified parameter resets that permission to its default value. The request must be authenticated with the admin API key. + * Replaces the permissions of an existing API key. Any unspecified attribute resets that attribute to its default value. * * Required API Key ACLs: * - admin. diff --git a/packages/recommend/model/anchoring.ts b/packages/recommend/model/anchoring.ts index c77a11939..cb727242e 100644 --- a/packages/recommend/model/anchoring.ts +++ b/packages/recommend/model/anchoring.ts @@ -1,6 +1,6 @@ // 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. /** - * Whether the pattern parameter matches the beginning (`startsWith`) or end (`endsWith`) of the query string, is an exact match (`is`), or a partial match (`contains`). + * Which part of the search query the pattern should match: - `startsWith`. The pattern must match the begginning of the query. - `endsWith`. The pattern must match the end of the query. - `is`. The pattern must match the query exactly. - `contains`. The pattern must match anywhere in the query. Empty queries are only allowed as pattern with `anchoring: is`. */ export type Anchoring = 'contains' | 'endsWith' | 'is' | 'startsWith'; diff --git a/packages/recommend/model/aroundPrecision.ts b/packages/recommend/model/aroundPrecision.ts index 71120c73e..937a1e87e 100644 --- a/packages/recommend/model/aroundPrecision.ts +++ b/packages/recommend/model/aroundPrecision.ts @@ -3,6 +3,6 @@ import type { AroundPrecisionFromValueInner } from './aroundPrecisionFromValueInner'; /** - * Precision of a geographical search (in meters), to [group results that are more or less the same distance from a central point](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/in-depth/geo-ranking-precision/). + * Precision of a coordinate-based search in meters to group results with similar distances. The Geo ranking criterion considers all matches within the same range of distances to be equal. */ export type AroundPrecision = AroundPrecisionFromValueInner[] | number; diff --git a/packages/recommend/model/aroundPrecisionFromValueInner.ts b/packages/recommend/model/aroundPrecisionFromValueInner.ts index 14a0e3bb7..c3850a800 100644 --- a/packages/recommend/model/aroundPrecisionFromValueInner.ts +++ b/packages/recommend/model/aroundPrecisionFromValueInner.ts @@ -1,7 +1,16 @@ // 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. +/** + * Range object with lower and upper values in meters to define custom ranges. + */ export type AroundPrecisionFromValueInner = { + /** + * Lower boundary of a range in meters. The Geo ranking criterion considers all records within the range to be equal. + */ from?: number; + /** + * Upper boundary of a range in meters. The Geo ranking criterion considers all records within the range to be equal. + */ value?: number; }; diff --git a/packages/recommend/model/aroundRadius.ts b/packages/recommend/model/aroundRadius.ts index 6c99817b2..1c4ae8df2 100644 --- a/packages/recommend/model/aroundRadius.ts +++ b/packages/recommend/model/aroundRadius.ts @@ -3,6 +3,6 @@ import type { AroundRadiusAll } from './aroundRadiusAll'; /** - * [Maximum radius](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#increase-the-search-radius) for a geographical search (in meters). + * Maximum radius for a search around a central location. This parameter works in combination with the `aroundLatLng` and `aroundLatLngViaIP` parameters. By default, the search radius is determined automatically from the density of hits around the central location. The search radius is small if there are many hits close to the central coordinates. */ export type AroundRadius = AroundRadiusAll | number; diff --git a/packages/recommend/model/aroundRadiusAll.ts b/packages/recommend/model/aroundRadiusAll.ts index 1dd22ed57..e5f107060 100644 --- a/packages/recommend/model/aroundRadiusAll.ts +++ b/packages/recommend/model/aroundRadiusAll.ts @@ -1,3 +1,6 @@ // 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. +/** + * Return all records with a valid `_geoloc` attribute. Don\'t filter by distance. + */ export type AroundRadiusAll = 'all'; diff --git a/packages/recommend/model/automaticFacetFilter.ts b/packages/recommend/model/automaticFacetFilter.ts index 98a2e1e7a..ca83695bf 100644 --- a/packages/recommend/model/automaticFacetFilter.ts +++ b/packages/recommend/model/automaticFacetFilter.ts @@ -1,21 +1,21 @@ // 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. /** - * Automatic facet Filter. + * Filter or optional filter to be applied to the search. */ export type AutomaticFacetFilter = { /** - * Attribute to filter on. This must match a facet placeholder in the Rule\'s pattern. + * Facet name to be applied as filter. The name must match placeholders in the `pattern` parameter. For example, with `pattern: {facet:genre}`, `automaticFacetFilters` must be `genre`. */ facet: string; /** - * Score for the filter. Typically used for optional or disjunctive filters. + * Filter scores to give different weights to individual filters. */ score?: number; /** - * Whether the filter is disjunctive (true) or conjunctive (false). + * Whether the filter is disjunctive or conjunctive. If true the filter has multiple matches, multiple occurences are combined with the logical `OR` operation. If false, multiple occurences are combined with the logical `AND` operation. */ disjunctive?: boolean; }; diff --git a/packages/recommend/model/automaticFacetFilters.ts b/packages/recommend/model/automaticFacetFilters.ts index 0ac46a30f..725561f8d 100644 --- a/packages/recommend/model/automaticFacetFilters.ts +++ b/packages/recommend/model/automaticFacetFilters.ts @@ -3,6 +3,6 @@ import type { AutomaticFacetFilter } from './automaticFacetFilter'; /** - * Names of facets to which automatic filtering must be applied; they must match the facet name of a facet value placeholder in the query pattern. + * Filter to be applied to the search. You can use this to respond to search queries that match a facet value. For example, if users search for \"comedy\", which matches a facet value of the \"genre\" facet, you can filter the results to show the top-ranked comedy movies. */ export type AutomaticFacetFilters = AutomaticFacetFilter[] | string[]; diff --git a/packages/recommend/model/baseRecommendRequest.ts b/packages/recommend/model/baseRecommendRequest.ts index fee4851d3..0d0a6cd60 100644 --- a/packages/recommend/model/baseRecommendRequest.ts +++ b/packages/recommend/model/baseRecommendRequest.ts @@ -2,7 +2,7 @@ export type BaseRecommendRequest = { /** - * Algolia index name. + * Index name. */ indexName: string; diff --git a/packages/recommend/model/baseRecommendationsQuery.ts b/packages/recommend/model/baseRecommendationsQuery.ts index 66b9b50eb..19b95a895 100644 --- a/packages/recommend/model/baseRecommendationsQuery.ts +++ b/packages/recommend/model/baseRecommendationsQuery.ts @@ -7,7 +7,7 @@ export type BaseRecommendationsQuery = { model: RecommendationModels; /** - * Unique object identifier. + * Unique record identifier. */ objectID: string; diff --git a/packages/recommend/model/baseRecommendedForYouQueryParameters.ts b/packages/recommend/model/baseRecommendedForYouQueryParameters.ts index 6ea203296..a7735ead9 100644 --- a/packages/recommend/model/baseRecommendedForYouQueryParameters.ts +++ b/packages/recommend/model/baseRecommendedForYouQueryParameters.ts @@ -2,7 +2,7 @@ export type BaseRecommendedForYouQueryParameters = { /** - * Associates a [user token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken/) with the current search. + * 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; }; diff --git a/packages/recommend/model/baseSearchParamsWithoutQuery.ts b/packages/recommend/model/baseSearchParamsWithoutQuery.ts index 33825f13f..95ae5b039 100644 --- a/packages/recommend/model/baseSearchParamsWithoutQuery.ts +++ b/packages/recommend/model/baseSearchParamsWithoutQuery.ts @@ -9,12 +9,12 @@ import type { TagFilters } from './tagFilters'; export type BaseSearchParamsWithoutQuery = { /** - * Overrides the query parameter and performs a more generic search. + * 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](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering/) the query with numeric, facet, or tag filters. + * Filter the search so that only records with matching values are included in the results. These filters are supported: - **Numeric filters.** ` `, where `` is one of `<`, `<=`, `=`, `!=`, `>`, `>=`. - **Ranges.** `: TO ` where `` and `` are the lower and upper limits of the range (inclusive). - **Facet filters.** `:` where `` is a facet attribute (case-sensitive) and `` a facet value. - **Tag filters.** `_tags:` or just `` (case-sensitive). - **Boolean filters.** `: 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; @@ -27,47 +27,47 @@ export type BaseSearchParamsWithoutQuery = { tagFilters?: TagFilters; /** - * Determines how to calculate [filter scores](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering/in-depth/filter-scoring/#accumulating-scores-with-sumorfiltersscores). If `false`, maximum score is kept. If `true`, score is summed. + * 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 query to only look at a subset of your [searchable attributes](https://www.algolia.com/doc/guides/managing-results/must-do/searchable-attributes/). + * Restricts a search to a subset of your searchable attributes. */ restrictSearchableAttributes?: string[]; /** - * Returns [facets](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#contextual-facet-values-and-counts), their facet values, and the number of matching facet values. + * 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?: string[]; /** - * Forces faceting to be applied after [de-duplication](https://www.algolia.com/doc/guides/managing-results/refine-results/grouping/) (with the distinct feature). Alternatively, the `afterDistinct` [modifier](https://www.algolia.com/doc/api-reference/api-parameters/attributesForFaceting/#modifiers) of `attributesForFaceting` allows for more granular control. + * 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; /** - * Page to retrieve (the first page is `0`, not `1`). + * Page of search results to retrieve. */ page?: number; /** - * Specifies the offset of the first hit to return. > **Note**: Using `page` and `hitsPerPage` is the recommended method for [paging results](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/). However, you can use `offset` and `length` to implement [an alternative approach to paging](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/#retrieving-a-subset-of-records-with-offset-and-length). + * Position of the first hit to retrieve. */ offset?: number; /** - * Sets the number of hits to retrieve (for use with `offset`). > **Note**: Using `page` and `hitsPerPage` is the recommended method for [paging results](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/). However, you can use `offset` and `length` to implement [an alternative approach to paging](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/#retrieving-a-subset-of-records-with-offset-and-length). + * Number of hits to retrieve (used in combination with `offset`). */ length?: number; /** - * Search for entries [around a central location](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filter-around-a-central-point), enabling a geographical search within a circular area. + * Coordinates for the center of a circle, expressed as a comma-separated string of latitude and longitude. Only records included within 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; /** - * Search for entries around a location. The location is automatically computed from the requester\'s IP address. + * Whether to obtain the coordinates from the request\'s IP address. */ aroundLatLngViaIP?: boolean; @@ -76,62 +76,57 @@ export type BaseSearchParamsWithoutQuery = { aroundPrecision?: AroundPrecision; /** - * Minimum radius (in meters) used for a geographical search when `aroundRadius` isn\'t set. + * Minimum radius (in meters) for a search around a location when `aroundRadius` isn\'t set. */ minimumAroundRadius?: number; /** - * Search inside a [rectangular area](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas) (in geographical coordinates). + * 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?: number[][]; /** - * Search inside a [polygon](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas) (in geographical coordinates). + * 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?: number[][]; /** - * Changes the default values of parameters that work best for a natural language query, such as `ignorePlurals`, `removeStopWords`, `removeWordsIfNoResults`, `analyticsTags`, and `ruleContexts`. These parameters work well together when the query consists of fuller natural language strings instead of keywords, for example when processing voice search queries. + * 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?: string[]; /** - * Assigns [rule contexts](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/how-to/customize-search-results-by-platform/#whats-a-context) to search queries. + * 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?: string[]; /** - * Defines how much [Personalization affects results](https://www.algolia.com/doc/guides/personalization/personalizing-results/in-depth/configuring-personalization/#understanding-personalization-impact). + * 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; /** - * Associates a [user token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken/) with the current search. + * 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; /** - * Incidates whether the search response includes [detailed ranking information](https://www.algolia.com/doc/guides/building-search-ui/going-further/backend-search/in-depth/understanding-the-api-response/#ranking-information). + * Whether the search response should include detailed ranking information. */ getRankingInfo?: boolean; /** - * Enriches the API\'s response with information about how the query was processed. - */ - explain?: string[]; - - /** - * Whether to take into account an index\'s synonyms for a particular search. + * Whether to take into account an index\'s synonyms for this search. */ synonyms?: boolean; /** - * Indicates whether a query ID parameter is included in the search response. This is required for [tracking click and conversion events](https://www.algolia.com/doc/guides/sending-events/concepts/event-types/#events-related-to-algolia-requests). + * 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; /** - * Indicates whether this query will be included in [analytics](https://www.algolia.com/doc/guides/search-analytics/guides/exclude-queries/). + * Whether this search will be included in Analytics. */ analytics?: boolean; @@ -141,12 +136,12 @@ export type BaseSearchParamsWithoutQuery = { analyticsTags?: string[]; /** - * Whether to include or exclude a query from the processing-time percentile computation. + * Whether to include this search when calculating processing-time percentiles. */ percentileComputation?: boolean; /** - * Incidates whether this search will be considered in A/B testing. + * Whether to enable A/B testing for this search. */ enableABTest?: boolean; }; diff --git a/packages/recommend/model/baseSearchResponse.ts b/packages/recommend/model/baseSearchResponse.ts index abd29c39d..6d3dd06f9 100644 --- a/packages/recommend/model/baseSearchResponse.ts +++ b/packages/recommend/model/baseSearchResponse.ts @@ -22,7 +22,7 @@ export type BaseSearchResponse = Record & { aroundLatLng?: string; /** - * Automatically-computed radius. + * Distance from a central coordinate provided by `aroundLatLng`. */ automaticRadius?: string; @@ -44,7 +44,7 @@ export type BaseSearchResponse = Record & { exhaustiveTypo?: boolean; /** - * Mapping of each facet name to the corresponding facet counts. + * Facet counts. */ facets?: Record>; @@ -74,12 +74,12 @@ export type BaseSearchResponse = Record & { message?: string; /** - * Number of hits the search query matched. + * Number of results (hits). */ nbHits: number; /** - * Number of pages of results for the current query. + * Number of pages of results. */ nbPages: number; @@ -89,7 +89,7 @@ export type BaseSearchResponse = Record & { nbSortedHits?: number; /** - * Page to retrieve (the first page is `0`, not `1`). + * Page of search results to retrieve. */ page: number; @@ -128,7 +128,7 @@ export type BaseSearchResponse = Record & { serverUsed?: string; /** - * Lets you store custom data in your indices. + * An object with custom data. You can store up to 32 kB as custom data. */ userData?: any | null; diff --git a/packages/recommend/model/clientMethodProps.ts b/packages/recommend/model/clientMethodProps.ts index 652cfc511..2ba6a48fc 100644 --- a/packages/recommend/model/clientMethodProps.ts +++ b/packages/recommend/model/clientMethodProps.ts @@ -72,7 +72,7 @@ export type CustomPutProps = { */ export type DeleteRecommendRuleProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** @@ -80,7 +80,7 @@ export type DeleteRecommendRuleProps = { */ model: RecommendModels; /** - * Unique record (object) identifier. + * Unique record identifier. */ objectID: string; }; @@ -90,7 +90,7 @@ export type DeleteRecommendRuleProps = { */ export type GetRecommendRuleProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** @@ -98,7 +98,7 @@ export type GetRecommendRuleProps = { */ model: RecommendModels; /** - * Unique record (object) identifier. + * Unique record identifier. */ objectID: string; }; @@ -108,7 +108,7 @@ export type GetRecommendRuleProps = { */ export type GetRecommendStatusProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** @@ -126,7 +126,7 @@ export type GetRecommendStatusProps = { */ export type SearchRecommendRulesProps = { /** - * Index on which to perform the request. + * Name of the index on which to perform the operation. */ indexName: string; /** diff --git a/packages/recommend/model/condition.ts b/packages/recommend/model/condition.ts index bb600e8c4..fea1e6776 100644 --- a/packages/recommend/model/condition.ts +++ b/packages/recommend/model/condition.ts @@ -4,19 +4,24 @@ import type { Anchoring } from './anchoring'; export type Condition = { /** - * Query pattern syntax. + * Query pattern that triggers the rule. You can use either a literal string, or a special pattern `{facet:ATTRIBUTE}`, where `ATTRIBUTE` is a facet name. The rule is triggered if the query matches the literal string or a value of the specified facet. For example, with `pattern: {facet:genre}`, the rule is triggered when users search for a genre, such as \"comedy\". */ pattern?: string; anchoring?: Anchoring; /** - * Whether the pattern matches on plurals, synonyms, and typos. + * Whether the pattern should match plurals, synonyms, and typos. */ alternatives?: boolean; /** - * Rule context format: [A-Za-z0-9_-]+). + * An additional restriction that only triggers the rule, when the search has the same value as `ruleContexts` parameter. For example, if `context: mobile`, the rule is only triggered when the search request has a matching `ruleContexts: mobile`. A rule context must only contain alphanumeric characters. */ context?: string; + + /** + * Filters that trigger the rule. You can add add filters using the syntax `facet:value` so that the rule is triggered, when the specific filter is selected. You can use `filters` on its own or combine it with the `pattern` parameter. + */ + filters?: string; }; diff --git a/packages/recommend/model/consequence.ts b/packages/recommend/model/consequence.ts index be9aa688d..a24c7e3a8 100644 --- a/packages/recommend/model/consequence.ts +++ b/packages/recommend/model/consequence.ts @@ -5,28 +5,28 @@ import type { ConsequenceParams } from './consequenceParams'; import type { Promote } from './promote'; /** - * [Consequences](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/#consequences) of a rule. + * Effect of the rule. For more information, see [Consequences](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/#consequences). */ export type Consequence = { params?: ConsequenceParams; /** - * Records to promote. + * Records you want to pin to a specific position in the search results. You can promote up to 300 records, either individually, or as groups of up to 100 records each. */ promote?: Promote[]; /** - * Only use in combination with the `promote` consequence. When `true`, promoted results will be restricted to match the filters of the current search. When `false`, the promoted results will show up regardless of the filters. + * Whether promoted records must match an active filter for the consequence to be applied. This ensures that user actions (filtering the search) are given a higher precendence. For example, if you promote a record with the `color: red` attribute, and the user filters the search for `color: blue`, the \"red\" record won\'t be shown. */ filterPromotes?: boolean; /** - * Records to hide. By default, you can hide up to 50 records per rule. + * Records you want to hide from the search results. */ hide?: ConsequenceHide[]; /** - * Custom JSON object that will be appended to the userData array in the response. This object isn\'t interpreted by the API. It\'s limited to 1kB of minified JSON. + * A JSON object with custom data that will be appended to the `userData` array in the response. This object isn\'t interpreted by the API and is limited to 1 kB of minified JSON. */ userData?: any | null; }; diff --git a/packages/recommend/model/consequenceHide.ts b/packages/recommend/model/consequenceHide.ts index ff8731ed7..9ef5cf251 100644 --- a/packages/recommend/model/consequenceHide.ts +++ b/packages/recommend/model/consequenceHide.ts @@ -1,11 +1,11 @@ // 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. /** - * Unique identifier of the record to hide. + * Object ID of the record to hide. */ export type ConsequenceHide = { /** - * Unique object identifier. + * Unique record identifier. */ objectID: string; }; diff --git a/packages/recommend/model/consequenceQuery.ts b/packages/recommend/model/consequenceQuery.ts index 464cb5325..28d8722a3 100644 --- a/packages/recommend/model/consequenceQuery.ts +++ b/packages/recommend/model/consequenceQuery.ts @@ -3,6 +3,6 @@ import type { ConsequenceQueryObject } from './consequenceQueryObject'; /** - * When providing a string, it replaces the entire query string. When providing an object, it describes incremental edits to be made to the query string (but you can\'t do both). + * Replace or edit the search query. If `consequenceQuery` is a string, the entire search query is replaced with that string. If `consequenceQuery` is an object, it describes incremental edits made to the query. */ export type ConsequenceQuery = ConsequenceQueryObject | string; diff --git a/packages/recommend/model/consequenceQueryObject.ts b/packages/recommend/model/consequenceQueryObject.ts index 4aedb781e..6d12dbc8a 100644 --- a/packages/recommend/model/consequenceQueryObject.ts +++ b/packages/recommend/model/consequenceQueryObject.ts @@ -4,12 +4,12 @@ import type { Edit } from './edit'; export type ConsequenceQueryObject = { /** - * Words to remove. + * Words to remove from the search query. */ remove?: string[]; /** - * Edits to apply. + * Changes to make to the search query. */ edits?: Edit[]; }; diff --git a/packages/recommend/model/deletedAtResponse.ts b/packages/recommend/model/deletedAtResponse.ts index 58a016bde..f8ae3d95d 100644 --- a/packages/recommend/model/deletedAtResponse.ts +++ b/packages/recommend/model/deletedAtResponse.ts @@ -5,7 +5,7 @@ */ export type DeletedAtResponse = { /** - * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the `task` operation and this `taskID`. + * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run immediately. You can check the task\'s progress with the [`task` operation](#tag/Indices/operation/getTask) and this `taskID`. */ taskID: number; diff --git a/packages/recommend/model/distinct.ts b/packages/recommend/model/distinct.ts index 1779d9741..dc87dfb00 100644 --- a/packages/recommend/model/distinct.ts +++ b/packages/recommend/model/distinct.ts @@ -1,6 +1,6 @@ // 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. /** - * Enables [deduplication or grouping of results (Algolia\'s _distinct_ feature](https://www.algolia.com/doc/guides/managing-results/refine-results/grouping/#introducing-algolias-distinct-feature)). + * Determines how many records of a group are included in the search results. Records with the same value for the `attributeForDistinct` attribute are considered a group. The `distinct` setting controls how many members of the group are returned. This is useful for [deduplication and grouping](https://www.algolia.com/doc/guides/managing-results/refine-results/grouping/#introducing-algolias-distinct-feature). The `distinct` setting is ignored if `attributeForDistinct` is not set. */ export type Distinct = boolean | number; diff --git a/packages/recommend/model/edit.ts b/packages/recommend/model/edit.ts index 9c11afef4..b77d006e3 100644 --- a/packages/recommend/model/edit.ts +++ b/packages/recommend/model/edit.ts @@ -11,7 +11,7 @@ export type Edit = { delete?: string; /** - * Text that should be inserted in place of the removed text inside the query string. + * Text to be added in place of the deleted text inside the query string. */ insert?: string; }; diff --git a/packages/recommend/model/exactOnSingleWordQuery.ts b/packages/recommend/model/exactOnSingleWordQuery.ts index 6d5747887..bad4a2bae 100644 --- a/packages/recommend/model/exactOnSingleWordQuery.ts +++ b/packages/recommend/model/exactOnSingleWordQuery.ts @@ -1,6 +1,6 @@ // 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. /** - * Determines how 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) is computed when the query contains only one word. + * Determines how 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) is computed when the search query has only one word.
attribute
The Exact ranking criterion is 1 if the query word and attribute value are the same. For example, a search for \"road\" will match the value \"road\", but not \"road trip\".
none
The Exact ranking criterion is ignored on single-word searches.
word
The Exact ranking criterion is 1 if the query word is found in the attribute value. The query word must have at least 3 characters and must not be a stop word.
If `exactOnSingleWordQuery` is `word`, only exact matches will be highlighted, partial and prefix matches won\'t. */ export type ExactOnSingleWordQuery = 'attribute' | 'none' | 'word'; diff --git a/packages/recommend/model/facetFilters.ts b/packages/recommend/model/facetFilters.ts index e9eae1db3..f83f2eea3 100644 --- a/packages/recommend/model/facetFilters.ts +++ b/packages/recommend/model/facetFilters.ts @@ -3,6 +3,6 @@ import type { MixedSearchFilters } from './mixedSearchFilters'; /** - * [Filter hits by facet value](https://www.algolia.com/doc/api-reference/api-parameters/facetFilters/). + * Filter the search by facet values, so that only records with the same facet values are retrieved. **Prefer using the `filters` parameter, which supports all filter types and combinations with boolean operators.** - `[filter1, filter2]` is interpreted as `filter1 AND filter2`. - `[[filter1, filter2], filter3]` is interpreted as `filter1 OR filter2 AND filter3`. - `facet:-value` is interpreted as `NOT facet:value`. While it\'s best to avoid attributes that start with a `-`, you can still filter them by escaping with a backslash: `facet:\\-value`. */ export type FacetFilters = MixedSearchFilters[] | string; diff --git a/packages/recommend/model/facetOrdering.ts b/packages/recommend/model/facetOrdering.ts index 4e1af92fd..9e057ded5 100644 --- a/packages/recommend/model/facetOrdering.ts +++ b/packages/recommend/model/facetOrdering.ts @@ -4,13 +4,13 @@ import type { Facets } from './facets'; import type { Value } from './value'; /** - * Defines the ordering of facets (widgets). + * Order of facet names and facet values in your UI. */ export type FacetOrdering = { facets?: Facets; /** - * Ordering of facet values within an individual facet. + * Order of facet values. One object for each facet. */ values?: Record; }; diff --git a/packages/recommend/model/facets.ts b/packages/recommend/model/facets.ts index b10eb0f3c..3aefad3a5 100644 --- a/packages/recommend/model/facets.ts +++ b/packages/recommend/model/facets.ts @@ -1,11 +1,11 @@ // 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. /** - * Ordering of facets (widgets). + * Order of facet names. */ export type Facets = { /** - * Pinned order of facet lists. + * Explicit order of facets or facet values. This setting lets you always show specific facets or facet values at the top of the list. */ order?: string[]; }; diff --git a/packages/recommend/model/highlightResultOption.ts b/packages/recommend/model/highlightResultOption.ts index 7d68dce0e..0de083fe2 100644 --- a/packages/recommend/model/highlightResultOption.ts +++ b/packages/recommend/model/highlightResultOption.ts @@ -3,18 +3,18 @@ import type { MatchLevel } from './matchLevel'; /** - * Show highlighted section and words matched on a query. + * Surround words that match the query with HTML tags for highlighting. */ export type HighlightResultOption = { /** - * Markup text with `facetQuery` matches highlighted. + * Highlighted attribute value, including HTML tags. */ value: string; matchLevel: MatchLevel; /** - * List of words from the query that matched the object. + * List of matched words from the search query. */ matchedWords: string[]; diff --git a/packages/recommend/model/ignorePlurals.ts b/packages/recommend/model/ignorePlurals.ts index ffea12b13..e02272856 100644 --- a/packages/recommend/model/ignorePlurals.ts +++ b/packages/recommend/model/ignorePlurals.ts @@ -1,6 +1,6 @@ // 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. /** - * Treats singular, plurals, and other forms of declensions as matching terms. `ignorePlurals` is used in conjunction with the `queryLanguages` setting. _list_: language ISO codes for which ignoring plurals should be enabled. This list will override any values that you may have set in `queryLanguages`. _true_: enables the ignore plurals feature, where singulars and plurals are considered equivalent (\"foot\" = \"feet\"). The languages supported here are either [every language](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages/) (this is the default) or those set by `queryLanguages`. _false_: turns off the ignore plurals feature, so that singulars and plurals aren\'t considered to be the same (\"foot\" will not find \"feet\"). + * Treat singular, plurals, and other forms of declensions as equivalent. You should only use this feature for the languages used in your index. */ export type IgnorePlurals = string[] | boolean; diff --git a/packages/recommend/model/indexSettingsAsSearchParams.ts b/packages/recommend/model/indexSettingsAsSearchParams.ts index 765e380d1..b946517d8 100644 --- a/packages/recommend/model/indexSettingsAsSearchParams.ts +++ b/packages/recommend/model/indexSettingsAsSearchParams.ts @@ -16,47 +16,42 @@ import type { TypoTolerance } from './typoTolerance'; export type IndexSettingsAsSearchParams = { /** - * Attributes used for [faceting](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/) and the [modifiers](https://www.algolia.com/doc/api-reference/api-parameters/attributesForFaceting/#modifiers) that can be applied: `filterOnly`, `searchable`, and `afterDistinct`. - */ - attributesForFaceting?: string[]; - - /** - * Attributes to include in the API response. To reduce the size of your response, you can retrieve only some of the attributes. By default, the response includes all attributes. + * Attributes to include in the API response. To reduce the size of your response, you can retrieve only some of the attributes. - `*` 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?: string[]; /** - * Determines the order in which Algolia [returns your results](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/). + * 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?: string[]; /** - * Specifies the [Custom ranking criterion](https://www.algolia.com/doc/guides/managing-results/must-do/custom-ranking/). Use the `asc` and `desc` modifiers to specify the ranking order: ascending or descending. + * Attributes to use as [custom ranking](https://www.algolia.com/doc/guides/managing-results/must-do/custom-ranking/). The custom ranking attributes decide which items are shown first if the other ranking criteria are equal. Records with missing values for your selected custom ranking attributes are always sorted last. Boolean attributes are sorted based on their alphabetical order. **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.
If you use two or more custom ranking attributes, [reduce the precision](https://www.algolia.com/doc/guides/managing-results/must-do/custom-ranking/how-to/controlling-custom-ranking-metrics-precision/) of your first attributes, or the other attributes will never be applied. */ customRanking?: string[]; /** - * Relevancy threshold below which less relevant results aren\'t included in the results. + * 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. Strings that match the search query in the attributes are highlighted by surrounding them with HTML tags (`highlightPreTag` and `highlightPostTag`). + * Attributes to highlight. By default, all searchable attributes are highlighted. Use `*` to highlight all attributes or use an empty array `[]` to turn off highlighting. 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?: string[]; /** - * Attributes to _snippet_. \'Snippeting\' is shortening the attribute to a certain number of words. If not specified, the attribute is shortened to the 10 words around the matching string but you can specify the number. For example: `body:20`. + * Attributes for which to enable snippets. 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?: string[]; /** - * HTML string to insert before the highlighted parts in all highlight and snippet results. + * HTML tag to insert before the highlighted parts in all highlighted results and snippets. */ highlightPreTag?: string; /** - * HTML string to insert after the highlighted parts in all highlight and snippet results. + * HTML tag to insert after the highlighted parts in all highlighted results and snippets. */ highlightPostTag?: string; @@ -66,7 +61,7 @@ export type IndexSettingsAsSearchParams = { snippetEllipsisText?: string; /** - * Restrict highlighting and snippeting to items that matched the query. + * 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; @@ -76,24 +71,24 @@ export type IndexSettingsAsSearchParams = { hitsPerPage?: number; /** - * Minimum number of characters a word in the query string 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). + * 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 query string 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). + * 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 (\"numeric tokens\") in the query string. + * 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/). + * Attributes for which you want to turn off [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/). 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?: string[]; @@ -102,27 +97,27 @@ export type IndexSettingsAsSearchParams = { removeStopWords?: RemoveStopWords; /** - * Characters that the engine shouldn\'t automatically [normalize](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/normalization/). + * Characters for which diacritics should be preserved. By default, Algolia removes diacritics from letters. For example, `é` becomes `e`. If this causes issues in your search, you can specify characters that should keep their diacritics. */ keepDiacriticsOnCharacters?: string; /** - * Sets your user\'s search language. This adjusts language-specific settings and features such as `ignorePlurals`, `removeStopWords`, and [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) word detection. + * [ISO code](https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes) for language-specific settings such as plurals, stop words, 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?: string[]; /** - * [Splits compound words](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/#splitting-compound-words) into their component word parts in the query. + * Whether to split compound words 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. */ decompoundQuery?: boolean; /** - * Incidates whether [Rules](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/) are enabled. + * Whether to enable rules. */ enableRules?: boolean; /** - * Incidates whether [Personalization](https://www.algolia.com/doc/guides/personalization/what-is-personalization/) is enabled. + * Whether to enable Personalization. */ enablePersonalization?: boolean; @@ -135,51 +130,51 @@ export type IndexSettingsAsSearchParams = { semanticSearch?: SemanticSearch; /** - * Enables the [advanced query syntax](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/#advanced-syntax). + * Whether to support phrase matching and excluding words from search queries. Use the `advancedSyntaxFeatures` parameter to control which feature is supported. */ advancedSyntax?: boolean; /** - * Words which should be considered [optional](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/#creating-a-list-of-optional-words) when found in a query. + * 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 dividied 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?: string[]; /** - * 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). + * 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). This can be useful for attributes with long values, where the likelyhood 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?: string[]; exactOnSingleWordQuery?: ExactOnSingleWordQuery; /** - * Alternatives that should be considered an exact match by [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). + * 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.
. */ alternativesAsExact?: AlternativesAsExact[]; /** - * Allows you to specify which advanced syntax features are active when `advancedSyntax` is enabled. + * 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?: AdvancedSyntaxFeatures[]; distinct?: Distinct; /** - * Whether to highlight and snippet the original word that matches the synonym or the synonym itself. + * 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 occurences of \"house\" are replaced by \"home\" in the highlighted response. */ replaceSynonymsInHighlight?: boolean; /** - * Precision of the [proximity ranking criterion](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#proximity). + * 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; /** - * Attributes to include in the API response for search and browse queries. + * 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?: string[]; /** - * Maximum number of facet hits to return when [searching for facet values](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#search-for-facet-values). + * 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; @@ -189,19 +184,19 @@ export type IndexSettingsAsSearchParams = { maxValuesPerFacet?: number; /** - * Controls how facet values are fetched. + * 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; /** - * When the [Attribute criterion is ranked above Proximity](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#attribute-and-proximity-combinations) in your ranking formula, Proximity is used to select which searchable attribute is matched in the Attribute ranking stage. + * 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; /** - * Indicates whether this search will use [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking/). + * 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; diff --git a/packages/recommend/model/matchLevel.ts b/packages/recommend/model/matchLevel.ts index 771daa1fe..a5fa02991 100644 --- a/packages/recommend/model/matchLevel.ts +++ b/packages/recommend/model/matchLevel.ts @@ -1,6 +1,6 @@ // 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. /** - * Indicates how well the attribute matched the search query. + * Whether the whole query string matches or only a part. */ export type MatchLevel = 'full' | 'none' | 'partial'; diff --git a/packages/recommend/model/mode.ts b/packages/recommend/model/mode.ts index 128d51a2b..37ed88734 100644 --- a/packages/recommend/model/mode.ts +++ b/packages/recommend/model/mode.ts @@ -1,6 +1,6 @@ // 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. /** - * Search mode the index will use to query for results. + * Search mode the index will use to query for results. This setting only applies to indices, for which Algolia enabled NeuralSearch for you. */ export type Mode = 'keywordSearch' | 'neuralSearch'; diff --git a/packages/recommend/model/numericFilters.ts b/packages/recommend/model/numericFilters.ts index dde128ffc..3db0c89dc 100644 --- a/packages/recommend/model/numericFilters.ts +++ b/packages/recommend/model/numericFilters.ts @@ -3,6 +3,6 @@ import type { MixedSearchFilters } from './mixedSearchFilters'; /** - * [Filter on numeric attributes](https://www.algolia.com/doc/api-reference/api-parameters/numericFilters/). + * Filter by numeric facets. **Prefer using the `filters` parameter, which supports all filter types and combinations with boolean operators.** You can use numeric comparison operators: `<`, `<=`, `=`, `!=`, `>`, `>=`. Comparsions are precise up to 3 decimals. You can also provide ranges: `facet: TO `. The range includes the lower and upper boundaries. The same combination rules apply as for `facetFilters`. */ export type NumericFilters = MixedSearchFilters[] | string; diff --git a/packages/recommend/model/optionalFilters.ts b/packages/recommend/model/optionalFilters.ts index 1836d9315..f910cd0cf 100644 --- a/packages/recommend/model/optionalFilters.ts +++ b/packages/recommend/model/optionalFilters.ts @@ -3,6 +3,6 @@ import type { MixedSearchFilters } from './mixedSearchFilters'; /** - * Create filters to boost or demote records. Records that match the filter are ranked higher for positive and lower for negative optional filters. In contrast to regular filters, records that don\'t match the optional filter are still included in the results, only their ranking is affected. + * Filters to promote or demote records in the search results. Optional filters work like facet filters, but they don\'t exclude records from the search results. Records that match the optional filter rank before records that don\'t match. If you\'re using a negative filter `facet:-value`, matching records rank after records that don\'t match. - Optional filters don\'t work on virtual replicas. - Optional filters are applied _after_ sort-by attributes. - Optional filters don\'t work with numeric attributes. */ export type OptionalFilters = MixedSearchFilters[] | string; diff --git a/packages/recommend/model/params.ts b/packages/recommend/model/params.ts index dff37195c..8dbd02c2f 100644 --- a/packages/recommend/model/params.ts +++ b/packages/recommend/model/params.ts @@ -5,7 +5,7 @@ import type { ConsequenceQuery } from './consequenceQuery'; import type { RenderingContent } from './renderingContent'; /** - * Additional search parameters. + * Parameters to apply to this search. You can use all search parameters, plus special `automaticFacetFilters`, `automaticOptionalFacetFilters`, and `query`. */ export type Params = { query?: ConsequenceQuery; diff --git a/packages/recommend/model/promoteObjectID.ts b/packages/recommend/model/promoteObjectID.ts index aeb5e5e29..6e2f37992 100644 --- a/packages/recommend/model/promoteObjectID.ts +++ b/packages/recommend/model/promoteObjectID.ts @@ -5,12 +5,12 @@ */ export type PromoteObjectID = { /** - * Unique identifier of the record to promote. + * Unique record identifier. */ objectID: string; /** - * The position to promote the records to. If you pass objectIDs, the records are placed at this position as a group. For example, if you pronmote four objectIDs to position 0, the records take the first four positions. + * Position in the search results where you want to show the promoted records. */ position: number; }; diff --git a/packages/recommend/model/promoteObjectIDs.ts b/packages/recommend/model/promoteObjectIDs.ts index cfdaa6d76..01a5dd576 100644 --- a/packages/recommend/model/promoteObjectIDs.ts +++ b/packages/recommend/model/promoteObjectIDs.ts @@ -5,12 +5,12 @@ */ export type PromoteObjectIDs = { /** - * Unique identifiers of the records to promote. + * Object IDs of the records you want to promote. The records are placed as a group at the `position`. For example, if you want to promote four records to position `0`, they will be the first four search results. */ objectIDs: string[]; /** - * The position to promote the records to. If you pass objectIDs, the records are placed at this position as a group. For example, if you pronmote four objectIDs to position 0, the records take the first four positions. + * Position in the search results where you want to show the promoted records. */ position: number; }; diff --git a/packages/recommend/model/queryType.ts b/packages/recommend/model/queryType.ts index 50424749d..a609aca0e 100644 --- a/packages/recommend/model/queryType.ts +++ b/packages/recommend/model/queryType.ts @@ -1,6 +1,6 @@ // 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. /** - * Determines how query words are [interpreted as prefixes](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/in-depth/prefix-searching/). + * Determines if and how query words are interpreted as prefixes. By default, only the last query word is treated as prefix (`prefixLast`). To turn off prefix search, use `prefixNone`. Avoid `prefixAll`, which treats all query words as prefixes. This might lead to counterintuitive results and makes your search slower. For more information, see [Prefix searching](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/in-depth/prefix-searching/). */ export type QueryType = 'prefixAll' | 'prefixLast' | 'prefixNone'; diff --git a/packages/recommend/model/rankingInfo.ts b/packages/recommend/model/rankingInfo.ts index 71de0b00e..14edcdc59 100644 --- a/packages/recommend/model/rankingInfo.ts +++ b/packages/recommend/model/rankingInfo.ts @@ -3,14 +3,17 @@ import type { MatchedGeoLocation } from './matchedGeoLocation'; import type { Personalization } from './personalization'; +/** + * Object with detailed information about the record\'s ranking. + */ export type RankingInfo = { /** - * This field is reserved for advanced usage. + * Whether a filter matched the query. */ filters: number; /** - * Position of the most important matched attribute in the attributes to index list. + * Position of the first matched word in the best matching attribute of the record. */ firstMatchedWord: number; @@ -39,27 +42,27 @@ export type RankingInfo = { nbTypos: number; /** - * Present and set to true if a Rule promoted the hit. + * Whether the record was promoted by a rule. */ promoted: boolean; /** - * When the query contains more than one word, the sum of the distances between matched words (in meters). + * Number of words between multiple matches in the query plus 1. For single word queries, `proximityDistance` is 0. */ proximityDistance?: number; /** - * Custom ranking for the object, expressed as a single integer value. + * Overall ranking of the record, expressed as a single integer. This attribute is internal. */ userScore: number; /** - * Number of matched words, including prefixes and typos. + * Number of matched words. */ words: number; /** - * Wether the record are promoted by the re-ranking strategy. + * Whether the record is re-ranked. */ promotedByReRanking?: boolean; }; diff --git a/packages/recommend/model/reRankingApplyFilter.ts b/packages/recommend/model/reRankingApplyFilter.ts index 02a02545f..ced0223fd 100644 --- a/packages/recommend/model/reRankingApplyFilter.ts +++ b/packages/recommend/model/reRankingApplyFilter.ts @@ -3,6 +3,6 @@ import type { MixedSearchFilters } from './mixedSearchFilters'; /** - * When [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking/) is enabled, only records that match these filters will be affected by Dynamic Re-Ranking. + * Restrict [Dynamic Re-ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking/) to records that match these filters. */ export type ReRankingApplyFilter = MixedSearchFilters[] | string; diff --git a/packages/recommend/model/recommendHit.ts b/packages/recommend/model/recommendHit.ts index 937abae77..f504c1de3 100644 --- a/packages/recommend/model/recommendHit.ts +++ b/packages/recommend/model/recommendHit.ts @@ -9,17 +9,17 @@ import type { SnippetResult } from './snippetResult'; */ export type RecommendHit = Record & { /** - * Unique object identifier. + * Unique record identifier. */ objectID: string; /** - * Show highlighted section and words matched on a query. + * Surround words that match the query with HTML tags for highlighting. */ _highlightResult?: Record; /** - * Snippeted attributes show parts of the matched attributes. Only returned when attributesToSnippet is non-empty. + * Snippets that show the context around a matching search query. */ _snippetResult?: Record; diff --git a/packages/recommend/model/recommendationsHits.ts b/packages/recommend/model/recommendationsHits.ts index 537ff8bd2..296284c87 100644 --- a/packages/recommend/model/recommendationsHits.ts +++ b/packages/recommend/model/recommendationsHits.ts @@ -6,7 +6,7 @@ export type RecommendationsHits = { hits: RecommendationsHit[]; /** - * Text to search for in an index. + * Search query. */ query?: string; diff --git a/packages/recommend/model/removeStopWords.ts b/packages/recommend/model/removeStopWords.ts index 33f66341c..9bdbf9176 100644 --- a/packages/recommend/model/removeStopWords.ts +++ b/packages/recommend/model/removeStopWords.ts @@ -1,6 +1,6 @@ // 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. /** - * Removes stop (common) words from the query before executing it. `removeStopWords` is used in conjunction with the `queryLanguages` setting. _list_: language ISO codes for which stop words should be enabled. This list will override any values that you may have set in `queryLanguages`. _true_: enables the stop words feature, ensuring that stop words are removed from consideration in a search. The languages supported here are either [every language](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages/) (this is the default) or those set by `queryLanguages`. _false_: turns off the stop words feature, allowing stop words to be taken into account in a search. + * Removes stop words from the search query. Stop words are common words like articles, conjunctions, prepositions, or pronouns that have little or no meaning on their own. In English, \"the\", \"a\", or \"and\" are stop words. You should only use this feature for the languages used in your index. */ export type RemoveStopWords = string[] | boolean; diff --git a/packages/recommend/model/removeWordsIfNoResults.ts b/packages/recommend/model/removeWordsIfNoResults.ts index 2e5b6bdef..81519af90 100644 --- a/packages/recommend/model/removeWordsIfNoResults.ts +++ b/packages/recommend/model/removeWordsIfNoResults.ts @@ -1,7 +1,7 @@ // 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. /** - * Strategy to [remove words](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/in-depth/why-use-remove-words-if-no-results/) from the query when it doesn\'t match any hits. + * Strategy for removing words from the query when it doesn\'t return any results. This helps to avoid returning empty search results.
none
No words are removed when a query doesn\'t return results.
lastWords
Treat the last (then second to last, then third to last) word as optional, until there are results or at most 5 words have been removed.
firstWords
Treat the first (then second, then third) word as optional, until there are results or at most 5 words have been removed.
allOptional
Treat all words as optional.
For more information, see [Remove words to improve results](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/in-depth/why-use-remove-words-if-no-results/). */ export type RemoveWordsIfNoResults = | 'allOptional' diff --git a/packages/recommend/model/renderingContent.ts b/packages/recommend/model/renderingContent.ts index 9c632b96e..4385efd64 100644 --- a/packages/recommend/model/renderingContent.ts +++ b/packages/recommend/model/renderingContent.ts @@ -3,7 +3,7 @@ import type { FacetOrdering } from './facetOrdering'; /** - * Extra content for the search UI, for example, to control the [ordering and display of facets](https://www.algolia.com/doc/guides/managing-results/rules/merchandising-and-promoting/how-to/merchandising-facets/#merchandise-facets-and-their-values-in-the-manual-editor). You can set a default value and dynamically override it with [Rules](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/). + * Extra data that can be used in the search UI. You can use this to control aspects of your search UI, such as, the order of facet names and values without changing your frontend code. */ export type RenderingContent = { facetOrdering?: FacetOrdering; diff --git a/packages/recommend/model/searchParamsQuery.ts b/packages/recommend/model/searchParamsQuery.ts index 39058cbe1..9f1926f6c 100644 --- a/packages/recommend/model/searchParamsQuery.ts +++ b/packages/recommend/model/searchParamsQuery.ts @@ -2,7 +2,7 @@ export type SearchParamsQuery = { /** - * Text to search for in an index. + * Search query. */ query?: string; }; diff --git a/packages/recommend/model/searchRecommendRulesParams.ts b/packages/recommend/model/searchRecommendRulesParams.ts index f0aa68398..7cb2c0763 100644 --- a/packages/recommend/model/searchRecommendRulesParams.ts +++ b/packages/recommend/model/searchRecommendRulesParams.ts @@ -5,7 +5,7 @@ */ export type SearchRecommendRulesParams = { /** - * Full-text query. + * Search query. */ query?: string; @@ -15,7 +15,7 @@ export type SearchRecommendRulesParams = { context?: string; /** - * Requested page (the first page is page 0). + * Requested page of the API response. */ page?: number; diff --git a/packages/recommend/model/searchRecommendRulesResponse.ts b/packages/recommend/model/searchRecommendRulesResponse.ts index 2d760331b..1e6587548 100644 --- a/packages/recommend/model/searchRecommendRulesResponse.ts +++ b/packages/recommend/model/searchRecommendRulesResponse.ts @@ -9,17 +9,17 @@ export type SearchRecommendRulesResponse = { hits: RuleResponse[]; /** - * Number of hits the search query matched. + * Number of results (hits). */ nbHits: number; /** - * Page to retrieve (the first page is `0`, not `1`). + * Page of search results to retrieve. */ page: number; /** - * Number of pages of results for the current query. + * Number of pages of results. */ nbPages: number; }; diff --git a/packages/recommend/model/semanticSearch.ts b/packages/recommend/model/semanticSearch.ts index c9b832249..86cfd43a0 100644 --- a/packages/recommend/model/semanticSearch.ts +++ b/packages/recommend/model/semanticSearch.ts @@ -1,11 +1,11 @@ // 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. /** - * Settings for the semantic search part of NeuralSearch. Only used when `mode` is _neuralSearch_. + * Settings for the semantic search part of NeuralSearch. Only used when `mode` is `neuralSearch`. */ export type SemanticSearch = { /** - * Indices from which to collect click and conversion events. If null, the current index and replica group will be used as the event source. + * Indices from which to collect click and conversion events. If null, the current index and all its replicas are used. */ eventSources?: string[] | null; }; diff --git a/packages/recommend/model/snippetResultOption.ts b/packages/recommend/model/snippetResultOption.ts index cb21bd0f6..daab65f2d 100644 --- a/packages/recommend/model/snippetResultOption.ts +++ b/packages/recommend/model/snippetResultOption.ts @@ -3,11 +3,11 @@ import type { MatchLevel } from './matchLevel'; /** - * Snippeted attributes show parts of the matched attributes. Only returned when attributesToSnippet is non-empty. + * Snippets that show the context around a matching search query. */ export type SnippetResultOption = { /** - * Markup text with `facetQuery` matches highlighted. + * Highlighted attribute value, including HTML tags. */ value: string; diff --git a/packages/recommend/model/sortRemainingBy.ts b/packages/recommend/model/sortRemainingBy.ts index a5faf046e..7da7c289e 100644 --- a/packages/recommend/model/sortRemainingBy.ts +++ b/packages/recommend/model/sortRemainingBy.ts @@ -1,6 +1,6 @@ // 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. /** - * How to display the remaining items: - `count`: facet count (descending). - `alpha`: alphabetical (ascending). - `hidden`: show only pinned values. + * Order of facet values that aren\'t explicitly positioned with the `order` setting.
count
Order remaining facet values by decreasing count. The count is the number of matching records containing this facet value.
alpha
Sort facet values alphabetically.
hidden
Don\'t show facet values that aren\'t explicitly positioned.
. */ export type SortRemainingBy = 'alpha' | 'count' | 'hidden'; diff --git a/packages/recommend/model/tagFilters.ts b/packages/recommend/model/tagFilters.ts index 1b7e964bd..966082364 100644 --- a/packages/recommend/model/tagFilters.ts +++ b/packages/recommend/model/tagFilters.ts @@ -3,6 +3,6 @@ import type { MixedSearchFilters } from './mixedSearchFilters'; /** - * [Filter hits by tags](https://www.algolia.com/doc/api-reference/api-parameters/tagFilters/). + * Filter the search by values of the special `_tags` attribute. **Prefer using the `filters` parameter, which supports all filter types and combinations with boolean operators.** Different from regular facets, `_tags` can only be used for filtering (including or excluding records). You won\'t get a facet count. The same combination and escaping rules apply as for `facetFilters`. */ export type TagFilters = MixedSearchFilters[] | string; diff --git a/packages/recommend/model/taskStatus.ts b/packages/recommend/model/taskStatus.ts index 8f335ad21..169dd7bf2 100644 --- a/packages/recommend/model/taskStatus.ts +++ b/packages/recommend/model/taskStatus.ts @@ -1,6 +1,6 @@ // 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. /** - * _published_ if the task has been processed, _notPublished_ otherwise. + * Task status, `published` if the task is completed, `notPublished` otherwise. */ export type TaskStatus = 'notPublished' | 'published'; diff --git a/packages/recommend/model/typoTolerance.ts b/packages/recommend/model/typoTolerance.ts index 58ae716ef..0bd64036f 100644 --- a/packages/recommend/model/typoTolerance.ts +++ b/packages/recommend/model/typoTolerance.ts @@ -3,6 +3,6 @@ import type { TypoToleranceEnum } from './typoToleranceEnum'; /** - * Controls whether [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/) is enabled and how it is applied. + * Whether [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/) is enabled and how it is applied. If typo tolerance is true, `min`, or `strict`, [word splitting and concetenation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/splitting-and-concatenation/) is also active. */ export type TypoTolerance = TypoToleranceEnum | boolean; diff --git a/packages/recommend/model/typoToleranceEnum.ts b/packages/recommend/model/typoToleranceEnum.ts index 05cf7b62d..a33877b0d 100644 --- a/packages/recommend/model/typoToleranceEnum.ts +++ b/packages/recommend/model/typoToleranceEnum.ts @@ -1,3 +1,6 @@ // 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. +/** + * - `min`. Return matches with the lowest number of typos. For example, if you have matches without typos, only include those. But if there are no matches without typos (with 1 typo), include matches with 1 typo (2 typos). - `strict`. Return matches with the two lowest numbers of typos. With `strict`, the Typo ranking criterion is applied first in the `ranking` setting. + */ export type TypoToleranceEnum = 'min' | 'strict'; diff --git a/packages/recommend/model/value.ts b/packages/recommend/model/value.ts index 9bbf488f6..9054c5e5d 100644 --- a/packages/recommend/model/value.ts +++ b/packages/recommend/model/value.ts @@ -4,7 +4,7 @@ import type { SortRemainingBy } from './sortRemainingBy'; export type Value = { /** - * Pinned order of facet lists. + * Explicit order of facets or facet values. This setting lets you always show specific facets or facet values at the top of the list. */ order?: string[]; diff --git a/packages/recommend/src/recommendClient.ts b/packages/recommend/src/recommendClient.ts index b8b4c60e6..47e4bd41d 100644 --- a/packages/recommend/src/recommendClient.ts +++ b/packages/recommend/src/recommendClient.ts @@ -271,9 +271,9 @@ export function createRecommendClient({ * - editSettings. * * @param deleteRecommendRule - The deleteRecommendRule object. - * @param deleteRecommendRule.indexName - Index on which to perform the request. + * @param deleteRecommendRule.indexName - Name of the index on which to perform the operation. * @param deleteRecommendRule.model - [Recommend models](https://www.algolia.com/doc/guides/algolia-recommend/overview/#recommend-models). - * @param deleteRecommendRule.objectID - Unique record (object) identifier. + * @param deleteRecommendRule.objectID - Unique record identifier. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ deleteRecommendRule( @@ -323,9 +323,9 @@ export function createRecommendClient({ * - settings. * * @param getRecommendRule - The getRecommendRule object. - * @param getRecommendRule.indexName - Index on which to perform the request. + * @param getRecommendRule.indexName - Name of the index on which to perform the operation. * @param getRecommendRule.model - [Recommend models](https://www.algolia.com/doc/guides/algolia-recommend/overview/#recommend-models). - * @param getRecommendRule.objectID - Unique record (object) identifier. + * @param getRecommendRule.objectID - Unique record identifier. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. */ getRecommendRule( @@ -375,7 +375,7 @@ export function createRecommendClient({ * - editSettings. * * @param getRecommendStatus - The getRecommendStatus object. - * @param getRecommendStatus.indexName - Index on which to perform the request. + * @param getRecommendStatus.indexName - Name of the index on which to perform the operation. * @param getRecommendStatus.model - [Recommend models](https://www.algolia.com/doc/guides/algolia-recommend/overview/#recommend-models). * @param getRecommendStatus.taskID - Unique identifier of a task. Numeric value (up to 64bits). * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions. @@ -468,7 +468,7 @@ export function createRecommendClient({ * - settings. * * @param searchRecommendRules - The searchRecommendRules object. - * @param searchRecommendRules.indexName - Index on which to perform the request. + * @param searchRecommendRules.indexName - Name of the index on which to perform the operation. * @param searchRecommendRules.model - [Recommend models](https://www.algolia.com/doc/guides/algolia-recommend/overview/#recommend-models). * @param searchRecommendRules.searchRecommendRulesParams - The searchRecommendRulesParams object. * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions.