algolia 3.15.2 → 3.15.3

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 CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 2fe148871e84a4d80954a5d6bde5b88855ac4f9688c7771cd8cc8b8d94384fc4
4
- data.tar.gz: fb540475eea0e86db2a17730a5da5aa1c30c3f66f3c05fa3312fbe364d143691
3
+ metadata.gz: c521528574b41a25c37665a700bdf02e23c331b4ca5f6bcd0a20936f08d9dd17
4
+ data.tar.gz: aeff06d71c97b19e3b65ed8f96c9ba63bb0440565421c23d4e0f478dd9fb794d
5
5
  SHA512:
6
- metadata.gz: ffb449547ccec5dcf97cdadf4f532256bb09cee42658582c55fc1988148271a85f6dcb4db0ea7cc15e4a519c108603cd247f11261bf0fc152434ef23b0e524e6
7
- data.tar.gz: 8c738ccb5070a404fc39daaf032cc43f01cf084dbe747e41739ed4739d882cbbbbc8b41d0399c71df10bd796558cde1310a324f45fe072418c8dddaa7afc86d3
6
+ metadata.gz: d897aba85c6946a31218b83efd43ff7fa6be8492c8756ef14b12dae9b2bb98725df2f6dba12a7c91e6ef256c16ad59ab32037ba4a40bd01816e31cc55f564e6d
7
+ data.tar.gz: f8af17d8a81ff8cb9c5627f40573ed4f5fb465c33e7be7c6f42cceaa595f05bf8a8f90e8a81a9c5e111d00021bdc5f09be62b24422b32e2dfd1a0b4764cb9ea0
data/CHANGELOG.md CHANGED
@@ -1,3 +1,9 @@
1
+ ## [3.15.3](https://github.com/algolia/algoliasearch-client-ruby/compare/3.15.2...3.15.3)
2
+
3
+ - [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/)
4
+ - [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/)
5
+ - [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/)
6
+
1
7
  ## [3.15.2](https://github.com/algolia/algoliasearch-client-ruby/compare/3.15.1...3.15.2)
2
8
 
3
9
  - [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
@@ -1,7 +1,7 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- algolia (3.15.2)
4
+ algolia (3.15.3)
5
5
  base64 (>= 0.2.0, < 1)
6
6
  faraday (>= 1.0.1, < 3.0)
7
7
  faraday-net_http_persistent (>= 0.15, < 3)
@@ -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
@@ -189,7 +189,9 @@ module Algolia
189
189
  # List of attributes with nullable: true
190
190
  def self.openapi_nullable
191
191
  Set.new(
192
- []
192
+ [
193
+ :user_data
194
+ ]
193
195
  )
194
196
  end
195
197
 
@@ -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
 
@@ -443,6 +443,7 @@ module Algolia
443
443
  Set.new(
444
444
  [
445
445
  :inside_bounding_box,
446
+ :user_data,
446
447
  :optional_words
447
448
  ]
448
449
  )
@@ -444,6 +444,7 @@ module Algolia
444
444
  Set.new(
445
445
  [
446
446
  :inside_bounding_box,
447
+ :user_data,
447
448
  :optional_words
448
449
  ]
449
450
  )
@@ -174,7 +174,9 @@ module Algolia
174
174
  # List of attributes with nullable: true
175
175
  def self.openapi_nullable
176
176
  Set.new(
177
- []
177
+ [
178
+ :user_data
179
+ ]
178
180
  )
179
181
  end
180
182
 
@@ -190,7 +190,9 @@ module Algolia
190
190
  # List of attributes with nullable: true
191
191
  def self.openapi_nullable
192
192
  Set.new(
193
- []
193
+ [
194
+ :user_data
195
+ ]
194
196
  )
195
197
  end
196
198
 
@@ -318,6 +318,7 @@ module Algolia
318
318
  def self.openapi_nullable
319
319
  Set.new(
320
320
  [
321
+ :user_data,
321
322
  :optional_words
322
323
  ]
323
324
  )
@@ -187,7 +187,9 @@ module Algolia
187
187
  # List of attributes with nullable: true
188
188
  def self.openapi_nullable
189
189
  Set.new(
190
- []
190
+ [
191
+ :user_data
192
+ ]
191
193
  )
192
194
  end
193
195
 
@@ -322,6 +322,7 @@ module Algolia
322
322
  def self.openapi_nullable
323
323
  Set.new(
324
324
  [
325
+ :user_data,
325
326
  :optional_words
326
327
  ]
327
328
  )
@@ -3,5 +3,5 @@
3
3
  # 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.
4
4
 
5
5
  module Algolia
6
- VERSION = "3.15.2"
6
+ VERSION = "3.15.3"
7
7
  end
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.2
4
+ version: 3.15.3
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-03 00:00:00.000000000 Z
10
+ date: 2025-04-07 00:00:00.000000000 Z
11
11
  dependencies:
12
12
  - !ruby/object:Gem::Dependency
13
13
  name: faraday