algolia 3.15.2 → 3.15.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/CHANGELOG.md +14 -0
- data/Gemfile.lock +1 -1
- data/lib/algolia/api/search_client.rb +4 -4
- data/lib/algolia/models/composition/search_results_item.rb +3 -1
- data/lib/algolia/models/ingestion/event.rb +4 -1
- data/lib/algolia/models/ingestion/record_type.rb +2 -1
- data/lib/algolia/models/ingestion/source_docker.rb +1 -1
- data/lib/algolia/models/ingestion/watch_response.rb +2 -2
- data/lib/algolia/models/recommend/fallback_params.rb +1 -0
- data/lib/algolia/models/recommend/recommend_search_params.rb +1 -0
- data/lib/algolia/models/recommend/recommendations_results.rb +3 -1
- data/lib/algolia/models/search/browse_response.rb +3 -1
- data/lib/algolia/models/search/condition.rb +1 -1
- data/lib/algolia/models/search/index_settings.rb +1 -0
- data/lib/algolia/models/search/search_response.rb +3 -1
- data/lib/algolia/models/search/settings_response.rb +1 -0
- data/lib/algolia/transport/http/http_requester.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: 52cb63e14d4759337c66f9f2459f752ee03af7b7944b338783ee8797e989ddb6
|
4
|
+
data.tar.gz: 7b01e70ae34a17388540ae743ff93a5da87646c79f32fe811e38c9cc3e61f2ec
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: c98515c4ba5726fb4bb5871765ced01b3a7a9d92a85ddeab588a279d6bb68d4991c05b8d0eef5ba59f3be2a47d0c50ba75713f4d7eb165d5c000e9d0a89cfc07
|
7
|
+
data.tar.gz: a4ee881c2a812f5c0e9d643a109042ec8c7cda54d1766adab36f25c65d770fa84b93d862352db5f109f2a9c14bbc64080c6f96bb3afbb56423ac22558a2fc591
|
data/CHANGELOG.md
CHANGED
@@ -1,3 +1,17 @@
|
|
1
|
+
## [3.15.4](https://github.com/algolia/algoliasearch-client-ruby/compare/3.15.3...3.15.4)
|
2
|
+
|
3
|
+
- [369c14232](https://github.com/algolia/api-clients-automation/commit/369c14232) fix(specs): condition cant be numeric filter ([#4726](https://github.com/algolia/api-clients-automation/pull/4726)) by [@kai687](https://github.com/kai687/)
|
4
|
+
- [1911d224b](https://github.com/algolia/api-clients-automation/commit/1911d224b) fix(specs): event.status can be null ([#4727](https://github.com/algolia/api-clients-automation/pull/4727)) by [@millotp](https://github.com/millotp/)
|
5
|
+
- [a18b555b4](https://github.com/algolia/api-clients-automation/commit/a18b555b4) fix(specs): add missing recordType collection ([#4728](https://github.com/algolia/api-clients-automation/pull/4728)) by [@millotp](https://github.com/millotp/)
|
6
|
+
- [b8d187623](https://github.com/algolia/api-clients-automation/commit/b8d187623) fix(ruby): avoid mutating frozen string literals by replacing upcase! ([#4755](https://github.com/algolia/api-clients-automation/pull/4755)) by [@satoruk](https://github.com/satoruk/)
|
7
|
+
- [4570f18b8](https://github.com/algolia/api-clients-automation/commit/4570f18b8) fix(clients): correctly deserialize SearchResult ([#4756](https://github.com/algolia/api-clients-automation/pull/4756)) by [@millotp](https://github.com/millotp/)
|
8
|
+
|
9
|
+
## [3.15.3](https://github.com/algolia/algoliasearch-client-ruby/compare/3.15.2...3.15.3)
|
10
|
+
|
11
|
+
- [dbaef6696](https://github.com/algolia/api-clients-automation/commit/dbaef6696) fix(specs): userData is any type ([#4702](https://github.com/algolia/api-clients-automation/pull/4702)) by [@millotp](https://github.com/millotp/)
|
12
|
+
- [a922dca5a](https://github.com/algolia/api-clients-automation/commit/a922dca5a) docs(partialUpdate): add note about multiple operations ([#4721](https://github.com/algolia/api-clients-automation/pull/4721)) by [@Jerska](https://github.com/Jerska/)
|
13
|
+
- [e150cd934](https://github.com/algolia/api-clients-automation/commit/e150cd934) fix(specs): message is not required in WatchResponse ([#4723](https://github.com/algolia/api-clients-automation/pull/4723)) by [@millotp](https://github.com/millotp/)
|
14
|
+
|
1
15
|
## [3.15.2](https://github.com/algolia/algoliasearch-client-ruby/compare/3.15.1...3.15.2)
|
2
16
|
|
3
17
|
- [345e830176](https://github.com/algolia/api-clients-automation/commit/345e830176) fix(ruby): remove integer empty check ([#4698](https://github.com/algolia/api-clients-automation/pull/4698)) by [@lucas-aragno](https://github.com/lucas-aragno/)
|
data/Gemfile.lock
CHANGED
@@ -2062,7 +2062,7 @@ module Algolia
|
|
2062
2062
|
@api_client.deserialize(response.body, request_options[:debug_return_type] || "Search::UpdatedAtResponse")
|
2063
2063
|
end
|
2064
2064
|
|
2065
|
-
# Adds new attributes to a record, or updates 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, this operation replaces its first-level ancestor. To update an attribute without pushing the entire record, you can use these built-in operations. These operations can be helpful if you don't have access to your initial data. - Increment: increment a numeric attribute - Decrement: decrement a numeric attribute - Add: append a number or string element to an array attribute - Remove: remove all matching number or string elements from an array attribute made of numbers or strings - AddUnique: add a number or string element to an array attribute made of numbers or strings only if it's not already present - IncrementFrom: increment a numeric integer attribute only if the provided value matches the current value, and otherwise ignore the whole object update. For example, if you pass an IncrementFrom value of 2 for the version attribute, but the current value of the attribute is 1, the engine ignores the update. If the object doesn't exist, the engine only creates it if you pass an IncrementFrom value of 0. - IncrementSet: increment a numeric integer attribute only if the provided value is greater than the current value, and otherwise ignore the whole object update. For example, if you pass an IncrementSet value of 2 for the version attribute, and the current value of the attribute is 1, the engine updates the object. If the object doesn't exist yet, the engine only creates it if you pass an IncrementSet value greater than 0. You can specify an operation by providing an object with the attribute to update as the key and its value being an object with the following properties: - _operation: the operation to apply on the attribute - value: the right-hand side argument to the operation, for example, increment or decrement step, value to add or remove. This operation is subject to [indexing rate limits](https://support.algolia.com/hc/en-us/articles/4406975251089-Is-there-a-rate-limit-for-indexing-on-Algolia).
|
2065
|
+
# Adds new attributes to a record, or updates 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, this operation replaces its first-level ancestor. To update an attribute without pushing the entire record, you can use these built-in operations. These operations can be helpful if you don't have access to your initial data. - Increment: increment a numeric attribute - Decrement: decrement a numeric attribute - Add: append a number or string element to an array attribute - Remove: remove all matching number or string elements from an array attribute made of numbers or strings - AddUnique: add a number or string element to an array attribute made of numbers or strings only if it's not already present - IncrementFrom: increment a numeric integer attribute only if the provided value matches the current value, and otherwise ignore the whole object update. For example, if you pass an IncrementFrom value of 2 for the version attribute, but the current value of the attribute is 1, the engine ignores the update. If the object doesn't exist, the engine only creates it if you pass an IncrementFrom value of 0. - IncrementSet: increment a numeric integer attribute only if the provided value is greater than the current value, and otherwise ignore the whole object update. For example, if you pass an IncrementSet value of 2 for the version attribute, and the current value of the attribute is 1, the engine updates the object. If the object doesn't exist yet, the engine only creates it if you pass an IncrementSet value greater than 0. You can specify an operation by providing an object with the attribute to update as the key and its value being an object with the following properties: - _operation: the operation to apply on the attribute - value: the right-hand side argument to the operation, for example, increment or decrement step, value to add or remove. When updating multiple attributes or using multiple operations targeting the same record, you should use a single partial update for faster processing. This operation is subject to [indexing rate limits](https://support.algolia.com/hc/en-us/articles/4406975251089-Is-there-a-rate-limit-for-indexing-on-Algolia).
|
2066
2066
|
#
|
2067
2067
|
# Required API Key ACLs:
|
2068
2068
|
# - addObject
|
@@ -2114,7 +2114,7 @@ module Algolia
|
|
2114
2114
|
@api_client.call_api(:POST, path, new_options)
|
2115
2115
|
end
|
2116
2116
|
|
2117
|
-
# Adds new attributes to a record, or updates 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, this operation replaces its first-level ancestor. To update an attribute without pushing the entire record, you can use these built-in operations. These operations can be helpful if you don't have access to your initial data. - Increment: increment a numeric attribute - Decrement: decrement a numeric attribute - Add: append a number or string element to an array attribute - Remove: remove all matching number or string elements from an array attribute made of numbers or strings - AddUnique: add a number or string element to an array attribute made of numbers or strings only if it's not already present - IncrementFrom: increment a numeric integer attribute only if the provided value matches the current value, and otherwise ignore the whole object update. For example, if you pass an IncrementFrom value of 2 for the version attribute, but the current value of the attribute is 1, the engine ignores the update. If the object doesn't exist, the engine only creates it if you pass an IncrementFrom value of 0. - IncrementSet: increment a numeric integer attribute only if the provided value is greater than the current value, and otherwise ignore the whole object update. For example, if you pass an IncrementSet value of 2 for the version attribute, and the current value of the attribute is 1, the engine updates the object. If the object doesn't exist yet, the engine only creates it if you pass an IncrementSet value greater than 0. You can specify an operation by providing an object with the attribute to update as the key and its value being an object with the following properties: - _operation: the operation to apply on the attribute - value: the right-hand side argument to the operation, for example, increment or decrement step, value to add or remove. This operation is subject to [indexing rate limits](https://support.algolia.com/hc/en-us/articles/4406975251089-Is-there-a-rate-limit-for-indexing-on-Algolia).
|
2117
|
+
# Adds new attributes to a record, or updates 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, this operation replaces its first-level ancestor. To update an attribute without pushing the entire record, you can use these built-in operations. These operations can be helpful if you don't have access to your initial data. - Increment: increment a numeric attribute - Decrement: decrement a numeric attribute - Add: append a number or string element to an array attribute - Remove: remove all matching number or string elements from an array attribute made of numbers or strings - AddUnique: add a number or string element to an array attribute made of numbers or strings only if it's not already present - IncrementFrom: increment a numeric integer attribute only if the provided value matches the current value, and otherwise ignore the whole object update. For example, if you pass an IncrementFrom value of 2 for the version attribute, but the current value of the attribute is 1, the engine ignores the update. If the object doesn't exist, the engine only creates it if you pass an IncrementFrom value of 0. - IncrementSet: increment a numeric integer attribute only if the provided value is greater than the current value, and otherwise ignore the whole object update. For example, if you pass an IncrementSet value of 2 for the version attribute, and the current value of the attribute is 1, the engine updates the object. If the object doesn't exist yet, the engine only creates it if you pass an IncrementSet value greater than 0. You can specify an operation by providing an object with the attribute to update as the key and its value being an object with the following properties: - _operation: the operation to apply on the attribute - value: the right-hand side argument to the operation, for example, increment or decrement step, value to add or remove. When updating multiple attributes or using multiple operations targeting the same record, you should use a single partial update for faster processing. This operation is subject to [indexing rate limits](https://support.algolia.com/hc/en-us/articles/4406975251089-Is-there-a-rate-limit-for-indexing-on-Algolia).
|
2118
2118
|
#
|
2119
2119
|
# Required API Key ACLs:
|
2120
2120
|
# - addObject
|
@@ -2603,7 +2603,7 @@ module Algolia
|
|
2603
2603
|
@api_client.deserialize(response.body, request_options[:debug_return_type] || "Search::UpdatedAtResponse")
|
2604
2604
|
end
|
2605
2605
|
|
2606
|
-
# Sends multiple search requests 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.
|
2606
|
+
# Sends multiple search requests 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. Use the helper `searchForHits` or `searchForFacets` to get the results in a more convenient format, if you already know the return type you want.
|
2607
2607
|
#
|
2608
2608
|
# Required API Key ACLs:
|
2609
2609
|
# - search
|
@@ -2635,7 +2635,7 @@ module Algolia
|
|
2635
2635
|
@api_client.call_api(:POST, path, new_options)
|
2636
2636
|
end
|
2637
2637
|
|
2638
|
-
# Sends multiple search requests 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.
|
2638
|
+
# Sends multiple search requests 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. Use the helper `searchForHits` or `searchForFacets` to get the results in a more convenient format, if you already know the return type you want.
|
2639
2639
|
#
|
2640
2640
|
# Required API Key ACLs:
|
2641
2641
|
# - search
|
@@ -10,9 +10,10 @@ module Algolia
|
|
10
10
|
class RecordType
|
11
11
|
PRODUCT = "product".freeze
|
12
12
|
VARIANT = "variant".freeze
|
13
|
+
COLLECTION = "collection".freeze
|
13
14
|
|
14
15
|
def self.all_vars
|
15
|
-
@all_vars ||= [PRODUCT, VARIANT].freeze
|
16
|
+
@all_vars ||= [PRODUCT, VARIANT, COLLECTION].freeze
|
16
17
|
end
|
17
18
|
|
18
19
|
# Builds the enum from string
|
@@ -72,6 +72,8 @@ module Algolia
|
|
72
72
|
|
73
73
|
if attributes.key?(:run_id)
|
74
74
|
self.run_id = attributes[:run_id]
|
75
|
+
else
|
76
|
+
self.run_id = nil
|
75
77
|
end
|
76
78
|
|
77
79
|
if attributes.key?(:data)
|
@@ -88,8 +90,6 @@ module Algolia
|
|
88
90
|
|
89
91
|
if attributes.key?(:message)
|
90
92
|
self.message = attributes[:message]
|
91
|
-
else
|
92
|
-
self.message = nil
|
93
93
|
end
|
94
94
|
end
|
95
95
|
|
@@ -19,7 +19,7 @@ module Algolia
|
|
19
19
|
# 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.
|
20
20
|
attr_accessor :context
|
21
21
|
|
22
|
-
# Filters that trigger the rule. You can add
|
22
|
+
# Filters that trigger the rule. You can 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. You can't combine multiple filters with `OR` and you can't use numeric filters.
|
23
23
|
attr_accessor :filters
|
24
24
|
|
25
25
|
# Attribute mapping from ruby-style variable name to JSON key.
|
@@ -30,7 +30,7 @@ module Algolia
|
|
30
30
|
connection.options.open_timeout = connect_timeout / 1000
|
31
31
|
path += handle_query_params(query_params)
|
32
32
|
|
33
|
-
@logger.info("Sending #{method.to_s.upcase
|
33
|
+
@logger.info("Sending #{method.to_s.upcase} request to #{path} with body #{body}") if ENV["ALGOLIA_DEBUG"]
|
34
34
|
|
35
35
|
response = connection.run_request(method, path, body, headers)
|
36
36
|
|
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.15.
|
4
|
+
version: 3.15.4
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- https://alg.li/support
|
8
8
|
bindir: bin
|
9
9
|
cert_chain: []
|
10
|
-
date: 2025-04-
|
10
|
+
date: 2025-04-14 00:00:00.000000000 Z
|
11
11
|
dependencies:
|
12
12
|
- !ruby/object:Gem::Dependency
|
13
13
|
name: faraday
|