algolia 3.12.0 → 3.12.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +5 -0
- data/Gemfile.lock +1 -1
- data/lib/algolia/models/abtesting/list_ab_tests_response.rb +1 -1
- data/lib/algolia/models/recommend/fallback_params.rb +1 -1
- data/lib/algolia/models/recommend/recommend_search_params.rb +1 -1
- data/lib/algolia/models/recommend/trending_facets_query.rb +2 -4
- data/lib/algolia/models/search/browse_params_object.rb +1 -1
- data/lib/algolia/models/search/consequence.rb +1 -3
- data/lib/algolia/models/search/consequence_params.rb +1 -1
- data/lib/algolia/models/search/index_settings.rb +1 -1
- data/lib/algolia/models/search/search_for_facets.rb +1 -1
- data/lib/algolia/models/search/search_for_hits.rb +1 -1
- data/lib/algolia/models/search/search_params_object.rb +1 -1
- data/lib/algolia/models/search/settings_response.rb +1 -1
- data/lib/algolia/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 10077a28cc270e76616164f43144c53c3bdccd4335d22627b144ef0b718e97cc
|
4
|
+
data.tar.gz: ba7acf8de770caa1dfaf274a5c4cd0dfeaad8503e51592f98d8e8dad411d5138
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 9cbe483f389e43d6d83c3f2eb74f9e5c4a5320e5b4b18d71e95e646d8a588dda108c910c2f400a3f8d357905cae95ad064ddb45b256bcc33f11c64a7db729660
|
7
|
+
data.tar.gz: 63762aeb7d86bbaeded15f52cba5baa653bc2f3660c0a5a1de73cb81ad5a9685ce2f6a2b17b031e8bcb5749e2f0f3fdb361afc852f235c6d01b97687ca9ea585
|
data/CHANGELOG.md
CHANGED
@@ -1,3 +1,8 @@
|
|
1
|
+
## [3.12.1](https://github.com/algolia/algoliasearch-client-ruby/compare/3.12.0...3.12.1)
|
2
|
+
|
3
|
+
- [506b8a5636](https://github.com/algolia/api-clients-automation/commit/506b8a5636) fix(specs): responseFields description ([#4399](https://github.com/algolia/api-clients-automation/pull/4399)) by [@kai687](https://github.com/kai687/)
|
4
|
+
- [09e657fa76](https://github.com/algolia/api-clients-automation/commit/09e657fa76) fix(specs): add a linter to assert that type is present ([#4393](https://github.com/algolia/api-clients-automation/pull/4393)) by [@millotp](https://github.com/millotp/)
|
5
|
+
|
1
6
|
## [3.12.0](https://github.com/algolia/algoliasearch-client-ruby/compare/3.11.0...3.12.0)
|
2
7
|
|
3
8
|
- [5aa57630d6](https://github.com/algolia/api-clients-automation/commit/5aa57630d6) feat(specs): only use shortname in the source input ([#4287](https://github.com/algolia/api-clients-automation/pull/4287)) by [@millotp](https://github.com/millotp/)
|
data/Gemfile.lock
CHANGED
@@ -233,7 +233,7 @@ module Algolia
|
|
233
233
|
# 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.
|
234
234
|
attr_accessor :min_proximity
|
235
235
|
|
236
|
-
# Properties to include in the API response of
|
236
|
+
# 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 properties should be included. An empty list may lead to an empty API response (except properties you can't exclude). You can't exclude these properties: `message`, `warning`, `cursor`, `abTestVariantID`, or any property added by setting `getRankingInfo` to true. Your search depends on the `hits` field. If you omit this field, searches won't return any results. Your UI might also depend on other properties, for example, for pagination. Before restricting the response size, check the impact on your search experience.
|
237
237
|
attr_accessor :response_fields
|
238
238
|
|
239
239
|
# Maximum number of facet values to return for each facet.
|
@@ -234,7 +234,7 @@ module Algolia
|
|
234
234
|
# 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.
|
235
235
|
attr_accessor :min_proximity
|
236
236
|
|
237
|
-
# Properties to include in the API response of
|
237
|
+
# 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 properties should be included. An empty list may lead to an empty API response (except properties you can't exclude). You can't exclude these properties: `message`, `warning`, `cursor`, `abTestVariantID`, or any property added by setting `getRankingInfo` to true. Your search depends on the `hits` field. If you omit this field, searches won't return any results. Your UI might also depend on other properties, for example, for pagination. Before restricting the response size, check the impact on your search experience.
|
238
238
|
attr_accessor :response_fields
|
239
239
|
|
240
240
|
# Maximum number of facet values to return for each facet.
|
@@ -46,7 +46,7 @@ module Algolia
|
|
46
46
|
:threshold => :"Float",
|
47
47
|
:max_recommendations => :"Integer",
|
48
48
|
:query_parameters => :"RecommendSearchParams",
|
49
|
-
:facet_name => :"
|
49
|
+
:facet_name => :"String",
|
50
50
|
:model => :"TrendingFacetsModel",
|
51
51
|
:fallback_parameters => :"FallbackParams"
|
52
52
|
}
|
@@ -55,9 +55,7 @@ module Algolia
|
|
55
55
|
# List of attributes with nullable: true
|
56
56
|
def self.openapi_nullable
|
57
57
|
Set.new(
|
58
|
-
[
|
59
|
-
:facet_name
|
60
|
-
]
|
58
|
+
[]
|
61
59
|
)
|
62
60
|
end
|
63
61
|
|
@@ -189,7 +189,7 @@ module Algolia
|
|
189
189
|
# 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.
|
190
190
|
attr_accessor :min_proximity
|
191
191
|
|
192
|
-
# Properties to include in the API response of
|
192
|
+
# 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 properties should be included. An empty list may lead to an empty API response (except properties you can't exclude). You can't exclude these properties: `message`, `warning`, `cursor`, `abTestVariantID`, or any property added by setting `getRankingInfo` to true. Your search depends on the `hits` field. If you omit this field, searches won't return any results. Your UI might also depend on other properties, for example, for pagination. Before restricting the response size, check the impact on your search experience.
|
193
193
|
attr_accessor :response_fields
|
194
194
|
|
195
195
|
# Maximum number of facet values to return for each facet.
|
@@ -186,7 +186,7 @@ module Algolia
|
|
186
186
|
# 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.
|
187
187
|
attr_accessor :min_proximity
|
188
188
|
|
189
|
-
# Properties to include in the API response of
|
189
|
+
# 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 properties should be included. An empty list may lead to an empty API response (except properties you can't exclude). You can't exclude these properties: `message`, `warning`, `cursor`, `abTestVariantID`, or any property added by setting `getRankingInfo` to true. Your search depends on the `hits` field. If you omit this field, searches won't return any results. Your UI might also depend on other properties, for example, for pagination. Before restricting the response size, check the impact on your search experience.
|
190
190
|
attr_accessor :response_fields
|
191
191
|
|
192
192
|
# Maximum number of facet values to return for each facet.
|
@@ -161,7 +161,7 @@ module Algolia
|
|
161
161
|
# 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.
|
162
162
|
attr_accessor :min_proximity
|
163
163
|
|
164
|
-
# Properties to include in the API response of
|
164
|
+
# 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 properties should be included. An empty list may lead to an empty API response (except properties you can't exclude). You can't exclude these properties: `message`, `warning`, `cursor`, `abTestVariantID`, or any property added by setting `getRankingInfo` to true. Your search depends on the `hits` field. If you omit this field, searches won't return any results. Your UI might also depend on other properties, for example, for pagination. Before restricting the response size, check the impact on your search experience.
|
165
165
|
attr_accessor :response_fields
|
166
166
|
|
167
167
|
# Maximum number of facet values to return for each facet.
|
@@ -192,7 +192,7 @@ module Algolia
|
|
192
192
|
# 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.
|
193
193
|
attr_accessor :min_proximity
|
194
194
|
|
195
|
-
# Properties to include in the API response of
|
195
|
+
# 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 properties should be included. An empty list may lead to an empty API response (except properties you can't exclude). You can't exclude these properties: `message`, `warning`, `cursor`, `abTestVariantID`, or any property added by setting `getRankingInfo` to true. Your search depends on the `hits` field. If you omit this field, searches won't return any results. Your UI might also depend on other properties, for example, for pagination. Before restricting the response size, check the impact on your search experience.
|
196
196
|
attr_accessor :response_fields
|
197
197
|
|
198
198
|
# Maximum number of facet values to return for each facet.
|
@@ -192,7 +192,7 @@ module Algolia
|
|
192
192
|
# 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.
|
193
193
|
attr_accessor :min_proximity
|
194
194
|
|
195
|
-
# Properties to include in the API response of
|
195
|
+
# 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 properties should be included. An empty list may lead to an empty API response (except properties you can't exclude). You can't exclude these properties: `message`, `warning`, `cursor`, `abTestVariantID`, or any property added by setting `getRankingInfo` to true. Your search depends on the `hits` field. If you omit this field, searches won't return any results. Your UI might also depend on other properties, for example, for pagination. Before restricting the response size, check the impact on your search experience.
|
196
196
|
attr_accessor :response_fields
|
197
197
|
|
198
198
|
# Maximum number of facet values to return for each facet.
|
@@ -190,7 +190,7 @@ module Algolia
|
|
190
190
|
# 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.
|
191
191
|
attr_accessor :min_proximity
|
192
192
|
|
193
|
-
# Properties to include in the API response of
|
193
|
+
# 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 properties should be included. An empty list may lead to an empty API response (except properties you can't exclude). You can't exclude these properties: `message`, `warning`, `cursor`, `abTestVariantID`, or any property added by setting `getRankingInfo` to true. Your search depends on the `hits` field. If you omit this field, searches won't return any results. Your UI might also depend on other properties, for example, for pagination. Before restricting the response size, check the impact on your search experience.
|
194
194
|
attr_accessor :response_fields
|
195
195
|
|
196
196
|
# Maximum number of facet values to return for each facet.
|
@@ -160,7 +160,7 @@ module Algolia
|
|
160
160
|
# 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.
|
161
161
|
attr_accessor :min_proximity
|
162
162
|
|
163
|
-
# Properties to include in the API response of
|
163
|
+
# 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 properties should be included. An empty list may lead to an empty API response (except properties you can't exclude). You can't exclude these properties: `message`, `warning`, `cursor`, `abTestVariantID`, or any property added by setting `getRankingInfo` to true. Your search depends on the `hits` field. If you omit this field, searches won't return any results. Your UI might also depend on other properties, for example, for pagination. Before restricting the response size, check the impact on your search experience.
|
164
164
|
attr_accessor :response_fields
|
165
165
|
|
166
166
|
# Maximum number of facet values to return for each facet.
|
data/lib/algolia/version.rb
CHANGED
metadata
CHANGED
@@ -1,13 +1,13 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: algolia
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 3.12.
|
4
|
+
version: 3.12.1
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- https://alg.li/support
|
8
8
|
bindir: bin
|
9
9
|
cert_chain: []
|
10
|
-
date: 2025-
|
10
|
+
date: 2025-02-05 00:00:00.000000000 Z
|
11
11
|
dependencies:
|
12
12
|
- !ruby/object:Gem::Dependency
|
13
13
|
name: faraday
|