You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Sources/Recommend/Models/BaseRecommendIndexSettings.swift
+2-23Lines changed: 2 additions & 23 deletions
Original file line number
Diff line number
Diff line change
@@ -86,19 +86,7 @@ public struct BaseRecommendIndexSettings: Codable, JSONEncodable {
86
86
/// Whether to support phrase matching and excluding words from search queries. Use the `advancedSyntaxFeatures`
87
87
/// parameter to control which feature is supported.
88
88
publicvaradvancedSyntax:Bool?
89
-
/// Words that should be considered optional when found in the query. By default, records must match all words in
90
-
/// the search query to be included in the search results. Adding optional words can help to increase the number of
91
-
/// search results by running an additional search query that doesn't include the optional words. For example, if
92
-
/// the search query is \"action video\" and \"video\" is an optional word, the search engine runs two queries. One
93
-
/// for \"action video\" and one for \"action\". Records that match all words are ranked higher. For a search query
94
-
/// with 4 or more words **and** all its words are optional, the number of matched words required for a record to be
95
-
/// included in the search results increases for every 1,000 records: - If `optionalWords` has less than 10 words,
96
-
/// the required number of matched words increases by 1: results 1 to 1,000 require 1 matched word, results 1,001
97
-
/// to 2000 need 2 matched words. - If `optionalWords` has 10 or more words, the number of required matched words
98
-
/// increases by the number of optional words divided by 5 (rounded down). For example, with 18 optional words:
99
-
/// results 1 to 1,000 require 1 matched word, results 1,001 to 2000 need 4 matched words. For more information,
100
-
/// see [Optional words](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/#creating-a-list-of-optional-words).
101
-
publicvaroptionalWords:[String]?
89
+
publicvaroptionalWords:RecommendOptionalWords?
102
90
/// 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).
103
91
/// Attribute names are case-sensitive. This can be useful for attributes with long values, where the likelihood of
104
92
/// an exact match is high, such as product descriptions. Turning off the Exact ranking criterion for these
@@ -138,9 +126,6 @@ public struct BaseRecommendIndexSettings: Codable, JSONEncodable {
138
126
/// `parsedQuery`, or any property triggered by the `getRankingInfo` parameter. Don't exclude properties that you
139
127
/// might need in your search UI.
140
128
publicvarresponseFields:[String]?
141
-
/// Maximum number of facet values to return when [searching for facet
/// Minimum radius (in meters) for a search around a location when `aroundRadius` isn't set.
57
57
publicvarminimumAroundRadius:Int?
58
-
/// Coordinates for a rectangular area in which to search. Each bounding box is defined by the two opposite points
59
-
/// of its diagonal, and expressed as latitude and longitude pair: `[p1 lat, p1 long, p2 lat, p2 long]`. Provide
60
-
/// 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).
/// Minimum radius (in meters) for a search around a location when `aroundRadius` isn't set.
57
57
publicvarminimumAroundRadius:Int?
58
-
/// Coordinates for a rectangular area in which to search. Each bounding box is defined by the two opposite points
59
-
/// of its diagonal, and expressed as latitude and longitude pair: `[p1 lat, p1 long, p2 lat, p2 long]`. Provide
60
-
/// 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).
/// Attributes to include in the API response. To reduce the size of your response, you can retrieve only some of
193
193
/// the attributes. Attribute names are case-sensitive. - `*` retrieves all attributes, except attributes included
194
194
/// in the `customRanking` and `unretrievableAttributes` settings. - To retrieve all attributes except a specific
@@ -268,19 +268,7 @@ public struct FallbackParams: Codable, JSONEncodable {
268
268
/// Whether to support phrase matching and excluding words from search queries. Use the `advancedSyntaxFeatures`
269
269
/// parameter to control which feature is supported.
270
270
publicvaradvancedSyntax:Bool?
271
-
/// Words that should be considered optional when found in the query. By default, records must match all words in
272
-
/// the search query to be included in the search results. Adding optional words can help to increase the number of
273
-
/// search results by running an additional search query that doesn't include the optional words. For example, if
274
-
/// the search query is \"action video\" and \"video\" is an optional word, the search engine runs two queries. One
275
-
/// for \"action video\" and one for \"action\". Records that match all words are ranked higher. For a search query
276
-
/// with 4 or more words **and** all its words are optional, the number of matched words required for a record to be
277
-
/// included in the search results increases for every 1,000 records: - If `optionalWords` has less than 10 words,
278
-
/// the required number of matched words increases by 1: results 1 to 1,000 require 1 matched word, results 1,001
279
-
/// to 2000 need 2 matched words. - If `optionalWords` has 10 or more words, the number of required matched words
280
-
/// increases by the number of optional words divided by 5 (rounded down). For example, with 18 optional words:
281
-
/// results 1 to 1,000 require 1 matched word, results 1,001 to 2000 need 4 matched words. For more information,
282
-
/// see [Optional words](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/#creating-a-list-of-optional-words).
283
-
publicvaroptionalWords:[String]?
271
+
publicvaroptionalWords:RecommendOptionalWords?
284
272
/// 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).
285
273
/// Attribute names are case-sensitive. This can be useful for attributes with long values, where the likelihood of
286
274
/// an exact match is high, such as product descriptions. Turning off the Exact ranking criterion for these
@@ -320,9 +308,6 @@ public struct FallbackParams: Codable, JSONEncodable {
320
308
/// `parsedQuery`, or any property triggered by the `getRankingInfo` parameter. Don't exclude properties that you
321
309
/// might need in your search UI.
322
310
publicvarresponseFields:[String]?
323
-
/// Maximum number of facet values to return when [searching for facet
0 commit comments