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/Composition/Models/BaseInjectionQueryParameters.swift
+9-9Lines changed: 9 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ public struct BaseInjectionQueryParameters: Codable, JSONEncodable {
39
39
/// attributes or use an empty array `[]` to turn off highlighting. Attribute names are case-sensitive With
40
40
/// highlighting, strings that match the search query are surrounded by HTML tags defined by `highlightPreTag` and
41
41
/// `highlightPostTag`. You can use this to visually highlight matching parts of a search query in your UI For more
42
-
/// information, see [Highlighting and snippeting](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/highlighting-snippeting/js/).
42
+
/// information, see [Highlighting and snippeting](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/highlighting-snippeting/js).
43
43
publicvarattributesToHighlight:[String]?
44
44
/// Attributes to include in the API response To reduce the size of your response, you can retrieve only some of the
45
45
/// attributes. Attribute names are case-sensitive - `*` retrieves all attributes, except attributes included in the
@@ -54,7 +54,7 @@ public struct BaseInjectionQueryParameters: Codable, JSONEncodable {
54
54
publicvarattributesToSnippet:[String]?
55
55
/// Whether to include a `queryID` attribute in the response The query ID is a unique identifier for a search query
56
56
/// and is required for tracking [click and conversion
/// Whether to split compound words in the query into their building blocks For more information, see [Word segmentation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/#splitting-compound-words).
60
60
/// Word segmentation is supported for these languages: German, Dutch, Finnish, Swedish, and Norwegian.
@@ -69,8 +69,8 @@ public struct BaseInjectionQueryParameters: Codable, JSONEncodable {
69
69
/// lot of content on ranking.
70
70
publicvardisableExactOnAttributes:[String]?
71
71
/// Attributes for which you want to turn off [typo
/// Attribute names are case-sensitive Returning only exact matches can help when - [Searching in hyphenated attributes](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/how-to/how-to-search-in-hyphenated-attributes/).
/// Attribute names are case-sensitive Returning only exact matches can help when - [Searching in hyphenated attributes](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/how-to/how-to-search-in-hyphenated-attributes).
74
74
/// - Reducing the number of matches when you have too many. This can happen with attributes that are long blocks
75
75
/// of text, such as product descriptions Consider alternatives such as `disableTypoToleranceOnWords` or adding
76
76
/// synonyms if your attributes have intentional unusual spellings that might look like typos.
@@ -80,8 +80,8 @@ public struct BaseInjectionQueryParameters: Codable, JSONEncodable {
80
80
publicvarenableABTest:Bool?
81
81
/// Whether to enable Personalization.
82
82
publicvarenablePersonalization:Bool?
83
-
/// Whether this search will use [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking/)
84
-
/// This setting only has an effect if you activated Dynamic Re-Ranking for this index in the Algolia dashboard.
83
+
/// Whether this search will use [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking) This
84
+
/// setting only has an effect if you activated Dynamic Re-Ranking for this index in the Algolia dashboard.
85
85
publicvarenableReRanking:Bool?
86
86
/// Whether to enable rules.
87
87
publicvarenableRules:Bool?
@@ -99,7 +99,7 @@ public struct BaseInjectionQueryParameters: Codable, JSONEncodable {
99
99
/// supported:** `facet:value OR (facet:value AND facet:value)` Use quotes around your filters, if the facet
100
100
/// attribute name or facet value has spaces, keywords (`OR`, `AND`, `NOT`), or quotes. If a facet attribute is an
101
101
/// array, the filter matches if it matches at least one element of the array. For more information, see
/// Whether the search response should include detailed ranking information.
105
105
publicvargetRankingInfo:Bool?
@@ -136,9 +136,9 @@ public struct BaseInjectionQueryParameters: Codable, JSONEncodable {
136
136
/// dictionaries This setting sets a default list of languages used by the `removeStopWords` and `ignorePlurals`
137
137
/// 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)
138
138
/// languages. To support this, you must place the CJK language **first** **You should always specify a query
139
-
/// 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/),
139
+
/// 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),
140
140
/// or the languages you specified with the `ignorePlurals` or `removeStopWords` parameters. This can lead to
141
-
/// 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/).
141
+
/// 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).
@@ -57,9 +57,9 @@ public struct CompositionParams: Codable, JSONEncodable {
57
57
/// dictionaries This setting sets a default list of languages used by the `removeStopWords` and `ignorePlurals`
58
58
/// 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)
59
59
/// languages. To support this, you must place the CJK language **first** **You should always specify a query
60
-
/// 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/),
60
+
/// 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),
61
61
/// or the languages you specified with the `ignorePlurals` or `removeStopWords` parameters. This can lead to
62
-
/// 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/).
62
+
/// 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).
0 commit comments