algolia 3.27.0 → 3.28.0

data/lib/algolia/models/composition/facet_ordering.rb

@@ -214,8 +214,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/facet_stats.rb

@@ -232,8 +232,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/facets.rb

@@ -202,8 +202,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/get_task_response.rb

@@ -203,8 +203,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/highlight_result.rb

@@ -105,6 +105,5 @@ module Algolia
         end
       end
     end
-
   end
 end

data/lib/algolia/models/composition/highlight_result_option.rb

@@ -248,8 +248,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/hit.rb

@@ -253,8 +253,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/hit_metadata.rb

@@ -203,8 +203,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/hit_ranking_info.rb

@@ -364,8 +364,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/ignore_plurals.rb

@@ -106,6 +106,5 @@ module Algolia
         end
       end
     end
-
   end
 end

data/lib/algolia/models/composition/injected_item.rb

@@ -246,8 +246,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/injected_item_hits_metadata.rb

@@ -215,8 +215,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/injected_item_metadata.rb

@@ -202,8 +202,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/injected_item_source.rb

@@ -104,6 +104,5 @@ module Algolia
         end
       end
     end
-
   end
 end

data/lib/algolia/models/composition/injection.rb

@@ -13,11 +13,14 @@ module Algolia
       # list of injected items of the current Composition.
       attr_accessor :injected_items
 
+      attr_accessor :deduplication
+
       # Attribute mapping from ruby-style variable name to JSON key.
       def self.attribute_map
         {
           :main => :main,
-          :injected_items => :injectedItems
+          :injected_items => :injectedItems,
+          :deduplication => :deduplication
         }
       end
 
@@ -25,7 +28,8 @@ module Algolia
       def self.types_mapping
         {
           :main => :"Main",
-          :injected_items => :"Array<InjectedItem>"
+          :injected_items => :"Array<InjectedItem>",
+          :deduplication => :"Deduplication"
         }
       end
 
@@ -70,6 +74,10 @@ module Algolia
             self.injected_items = value
           end
         end
+
+        if attributes.key?(:deduplication)
+          self.deduplication = attributes[:deduplication]
+        end
       end
 
       # Checks equality by comparing each attribute.
@@ -78,7 +86,8 @@ module Algolia
         return true if self.equal?(other)
         self.class == other.class &&
           main == other.main &&
-          injected_items == other.injected_items
+          injected_items == other.injected_items &&
+          deduplication == other.deduplication
       end
 
       # @see the `==` method
@@ -90,7 +99,7 @@ module Algolia
       # Calculates hash code according to all attributes.
       # @return [Integer] Hash code
       def hash
-        [main, injected_items].hash
+        [main, injected_items, deduplication].hash
       end
 
       # Builds the object from hash
@@ -215,8 +224,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/inside_bounding_box.rb

@@ -104,6 +104,5 @@ module Algolia
         end
       end
     end
-
   end
 end

data/lib/algolia/models/composition/list_compositions_response.rb

@@ -254,8 +254,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/main.rb

@@ -200,8 +200,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/main_injection_query_parameters.rb

@@ -26,7 +26,7 @@ module Algolia
       # Whether the best matching attribute should be determined by minimum proximity This setting only affects ranking if the Attribute ranking criterion comes before Proximity in the `ranking` setting. If true, the best matching attribute is selected based on the minimum proximity of multiple matches. Otherwise, the best matching attribute is determined by the order in the `searchableAttributes` setting.
       attr_accessor :attribute_criteria_computed_by_min_proximity
 
-      # Attributes to highlight By default, all searchable attributes are highlighted. Use `*` to highlight all attributes or use an empty array `[]` to turn off highlighting. Attribute names are case-sensitive With highlighting, strings that match the search query are surrounded by HTML tags defined by `highlightPreTag` and `highlightPostTag`. You can use this to visually highlight matching parts of a search query in your UI For more information, see [Highlighting and snippeting](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/highlighting-snippeting/js/).
+      # Attributes to highlight By default, all searchable attributes are highlighted. Use `*` to highlight all attributes or use an empty array `[]` to turn off highlighting. Attribute names are case-sensitive With highlighting, strings that match the search query are surrounded by HTML tags defined by `highlightPreTag` and `highlightPostTag`. You can use this to visually highlight matching parts of a search query in your UI For more information, see [Highlighting and snippeting](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/highlighting-snippeting/js).
       attr_accessor :attributes_to_highlight
 
       # Attributes to include in the API response To reduce the size of your response, you can retrieve only some of the attributes. Attribute names are case-sensitive - `*` retrieves all attributes, except attributes included in the `customRanking` and `unretrievableAttributes` settings. - To retrieve all attributes except a specific one, prefix the attribute with a dash and combine it with the `*`: `[\"*\", \"-ATTRIBUTE\"]`. - The `objectID` attribute is always included.
@@ -35,7 +35,7 @@ module Algolia
       # Attributes for which to enable snippets. Attribute names are case-sensitive Snippets provide additional context to matched words. If you enable snippets, they include 10 words, including the matched word. The matched word will also be wrapped by HTML tags for highlighting. You can adjust the number of words with the following notation: `ATTRIBUTE:NUMBER`, where `NUMBER` is the number of words to be extracted.
       attr_accessor :attributes_to_snippet
 
-      # Whether to include a `queryID` attribute in the response The query ID is a unique identifier for a search query and is required for tracking [click and conversion events](https://www.algolia.com/guides/sending-events/getting-started/).
+      # Whether to include a `queryID` attribute in the response The query ID is a unique identifier for a search query and is required for tracking [click and conversion events](https://www.algolia.com/guides/sending-events/getting-started).
       attr_accessor :click_analytics
 
       # 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). Word segmentation is supported for these languages: German, Dutch, Finnish, Swedish, and Norwegian. Decompounding doesn't work for words with [non-spacing mark Unicode characters](https://www.charactercodes.net/category/non-spacing_mark). For example, `Gartenstühle` won't be decompounded if the `ü` consists of `u` (U+0075) and `◌̈` (U+0308).
@@ -44,7 +44,7 @@ module Algolia
       # 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). Attribute names are case-sensitive This can be useful for attributes with long values, where the likelihood of an exact match is high, such as product descriptions. Turning off the Exact ranking criterion for these attributes favors exact matching on other attributes. This reduces the impact of individual attributes with a lot of content on ranking.
       attr_accessor :disable_exact_on_attributes
 
-      # Attributes for which you want to turn off [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/). 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/). - Reducing the number of matches when you have too many.   This can happen with attributes that are long blocks of text, such as product descriptions Consider alternatives such as `disableTypoToleranceOnWords` or adding synonyms if your attributes have intentional unusual spellings that might look like typos.
+      # Attributes for which you want to turn off [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance). 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). - Reducing the number of matches when you have too many.   This can happen with attributes that are long blocks of text, such as product descriptions Consider alternatives such as `disableTypoToleranceOnWords` or adding synonyms if your attributes have intentional unusual spellings that might look like typos.
       attr_accessor :disable_typo_tolerance_on_attributes
 
       attr_accessor :distinct
@@ -55,7 +55,7 @@ module Algolia
       # Whether to enable Personalization.
       attr_accessor :enable_personalization
 
-      # Whether this search will use [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking/) This setting only has an effect if you activated Dynamic Re-Ranking for this index in the Algolia dashboard.
+      # Whether this search will use [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking) This setting only has an effect if you activated Dynamic Re-Ranking for this index in the Algolia dashboard.
       attr_accessor :enable_re_ranking
 
       # Whether to enable rules.
@@ -65,7 +65,7 @@ module Algolia
 
       attr_accessor :facet_filters
 
-      # Filter expression to only include items that match the filter criteria in the response.  You can use these filter expressions:  - **Numeric filters.** `<facet> <op> <number>`, where `<op>` is one of `<`, `<=`, `=`, `!=`, `>`, `>=`. - **Ranges.** `<facet>:<lower> TO <upper>` where `<lower>` and `<upper>` are the lower and upper limits of the range (inclusive). - **Facet filters.** `<facet>:<value>` where `<facet>` is a facet attribute (case-sensitive) and `<value>` a facet value. - **Tag filters.** `_tags:<value>` or just `<value>` (case-sensitive). - **Boolean filters.** `<facet>: true | false`.  You can combine filters with `AND`, `OR`, and `NOT` operators with the following restrictions:  - You can only combine filters of the same type with `OR`.   **Not supported:** `facet:value OR num > 3`. - You can't use `NOT` with combinations of filters.   **Not supported:** `NOT(facet:value OR facet:value)` - You can't combine conjunctions (`AND`) with `OR`.   **Not supported:** `facet:value OR (facet:value AND facet:value)`  Use quotes around your filters, if the facet attribute name or facet value has spaces, keywords (`OR`, `AND`, `NOT`), or quotes. If a facet attribute is an array, the filter matches if it matches at least one element of the array.  For more information, see [Filters](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering/).
+      # Filter expression to only include items that match the filter criteria in the response.  You can use these filter expressions:  - **Numeric filters.** `<facet> <op> <number>`, where `<op>` is one of `<`, `<=`, `=`, `!=`, `>`, `>=`. - **Ranges.** `<facet>:<lower> TO <upper>` where `<lower>` and `<upper>` are the lower and upper limits of the range (inclusive). - **Facet filters.** `<facet>:<value>` where `<facet>` is a facet attribute (case-sensitive) and `<value>` a facet value. - **Tag filters.** `_tags:<value>` or just `<value>` (case-sensitive). - **Boolean filters.** `<facet>: true | false`.  You can combine filters with `AND`, `OR`, and `NOT` operators with the following restrictions:  - You can only combine filters of the same type with `OR`.   **Not supported:** `facet:value OR num > 3`. - You can't use `NOT` with combinations of filters.   **Not supported:** `NOT(facet:value OR facet:value)` - You can't combine conjunctions (`AND`) with `OR`.   **Not supported:** `facet:value OR (facet:value AND facet:value)`  Use quotes around your filters, if the facet attribute name or facet value has spaces, keywords (`OR`, `AND`, `NOT`), or quotes. If a facet attribute is an array, the filter matches if it matches at least one element of the array.  For more information, see [Filters](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering).
       attr_accessor :filters
 
       # Whether the search response should include detailed ranking information.
@@ -106,7 +106,7 @@ module Algolia
       # Impact that Personalization should have on this search The higher this value is, the more Personalization determines the ranking compared to other factors. For more information, see [Understanding Personalization impact](https://www.algolia.com/doc/guides/personalization/personalizing-results/in-depth/configuring-personalization/#understanding-personalization-impact).
       attr_accessor :personalization_impact
 
-      # Languages for language-specific query processing steps such as plurals, stop-word removal, and word-detection dictionaries  This setting sets a default list of languages used by the `removeStopWords` and `ignorePlurals` 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) languages. To support this, you must place the CJK language **first**  **You should always specify a query 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/), or the languages you specified with the `ignorePlurals` or `removeStopWords` parameters. This can lead to 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/).
+      # Languages for language-specific query processing steps such as plurals, stop-word removal, and word-detection dictionaries  This setting sets a default list of languages used by the `removeStopWords` and `ignorePlurals` 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) languages. To support this, you must place the CJK language **first**  **You should always specify a query 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), or the languages you specified with the `ignorePlurals` or `removeStopWords` parameters. This can lead to 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).
       attr_accessor :query_languages
 
       attr_accessor :query_type
@@ -150,7 +150,7 @@ module Algolia
       # Maximum number of facet values to return for each facet.
       attr_accessor :max_values_per_facet
 
-      # Order in which to retrieve facet values - `count`.   Facet values are retrieved by decreasing count.   The count is the number of matching records containing this facet value - `alpha`.   Retrieve facet values alphabetically This setting doesn't influence how facet values are displayed in your UI (see `renderingContent`). For more information, see [facet value display](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/facet-display/js/).
+      # Order in which to retrieve facet values - `count`.   Facet values are retrieved by decreasing count.   The count is the number of matching records containing this facet value - `alpha`.   Retrieve facet values alphabetically This setting doesn't influence how facet values are displayed in your UI (see `renderingContent`). For more information, see [facet value display](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/facet-display/js).
       attr_accessor :sort_facet_values_by
 
       # Whether to sum all filter scores If true, all filter scores are summed. Otherwise, the maximum filter score is kept. For more information, see [filter scores](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering/in-depth/filter-scoring/#accumulating-scores-with-sumorfiltersscores).
@@ -800,8 +800,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/matched_geo_location.rb

@@ -222,8 +222,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/multiple_batch_request.rb

@@ -214,8 +214,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/multiple_batch_response.rb

@@ -206,8 +206,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/numeric_filters.rb

@@ -105,6 +105,5 @@ module Algolia
         end
       end
     end
-
   end
 end

data/lib/algolia/models/composition/optional_filters.rb

@@ -7,7 +7,7 @@ require "time"
 
 module Algolia
   module Composition
-    # Filters to promote or demote records in the search results.  Optional filters work like facet filters, but they don't exclude records from the search results. Records that match the optional filter rank before records that don't match. If you're using a negative filter `facet:-value`, matching records rank after records that don't match.  - Optional filters don't work on virtual replicas. - Optional filters are applied _after_ sort-by attributes. - Optional filters are applied _before_ custom ranking attributes (in the default [ranking](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/)). - Optional filters don't work with numeric attributes.
+    # Filters to promote or demote records in the search results.  Optional filters work like facet filters, but they don't exclude records from the search results. Records that match the optional filter rank before records that don't match. If you're using a negative filter `facet:-value`, matching records rank after records that don't match.  - Optional filters don't work on virtual replicas. - Optional filters are applied _after_ sort-by attributes. - Optional filters are applied _before_ custom ranking attributes (in the default [ranking](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria)). - Optional filters don't work with numeric attributes.
     module OptionalFilters
       class << self
       # List of class defined in oneOf (OpenAPI v3)
@@ -105,6 +105,5 @@ module Algolia
         end
       end
     end
-
   end
 end

data/lib/algolia/models/composition/optional_words.rb

@@ -105,6 +105,5 @@ module Algolia
         end
       end
     end
-
   end
 end

data/lib/algolia/models/composition/params.rb

@@ -11,7 +11,7 @@ module Algolia
       # Search query.
       attr_accessor :query
 
-      # Filter expression to only include items that match the filter criteria in the response.  You can use these filter expressions:  - **Numeric filters.** `<facet> <op> <number>`, where `<op>` is one of `<`, `<=`, `=`, `!=`, `>`, `>=`. - **Ranges.** `<facet>:<lower> TO <upper>` where `<lower>` and `<upper>` are the lower and upper limits of the range (inclusive). - **Facet filters.** `<facet>:<value>` where `<facet>` is a facet attribute (case-sensitive) and `<value>` a facet value. - **Tag filters.** `_tags:<value>` or just `<value>` (case-sensitive). - **Boolean filters.** `<facet>: true | false`.  You can combine filters with `AND`, `OR`, and `NOT` operators with the following restrictions:  - You can only combine filters of the same type with `OR`.   **Not supported:** `facet:value OR num > 3`. - You can't use `NOT` with combinations of filters.   **Not supported:** `NOT(facet:value OR facet:value)` - You can't combine conjunctions (`AND`) with `OR`.   **Not supported:** `facet:value OR (facet:value AND facet:value)`  Use quotes around your filters, if the facet attribute name or facet value has spaces, keywords (`OR`, `AND`, `NOT`), or quotes. If a facet attribute is an array, the filter matches if it matches at least one element of the array.  For more information, see [Filters](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering/).
+      # Filter expression to only include items that match the filter criteria in the response.  You can use these filter expressions:  - **Numeric filters.** `<facet> <op> <number>`, where `<op>` is one of `<`, `<=`, `=`, `!=`, `>`, `>=`. - **Ranges.** `<facet>:<lower> TO <upper>` where `<lower>` and `<upper>` are the lower and upper limits of the range (inclusive). - **Facet filters.** `<facet>:<value>` where `<facet>` is a facet attribute (case-sensitive) and `<value>` a facet value. - **Tag filters.** `_tags:<value>` or just `<value>` (case-sensitive). - **Boolean filters.** `<facet>: true | false`.  You can combine filters with `AND`, `OR`, and `NOT` operators with the following restrictions:  - You can only combine filters of the same type with `OR`.   **Not supported:** `facet:value OR num > 3`. - You can't use `NOT` with combinations of filters.   **Not supported:** `NOT(facet:value OR facet:value)` - You can't combine conjunctions (`AND`) with `OR`.   **Not supported:** `facet:value OR (facet:value AND facet:value)`  Use quotes around your filters, if the facet attribute name or facet value has spaces, keywords (`OR`, `AND`, `NOT`), or quotes. If a facet attribute is an array, the filter matches if it matches at least one element of the array.  For more information, see [Filters](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering).
       attr_accessor :filters
 
       # Page of search results to retrieve.
@@ -50,7 +50,7 @@ module Algolia
       # Coordinates of a polygon in which to search.  Polygons are defined by 3 to 10,000 points. Each point is represented by its latitude and longitude. Provide multiple polygons as nested arrays. For more information, see [filtering inside polygons](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas). This parameter is ignored if you also specify `insideBoundingBox`.
       attr_accessor :inside_polygon
 
-      # Languages for language-specific query processing steps such as plurals, stop-word removal, and word-detection dictionaries  This setting sets a default list of languages used by the `removeStopWords` and `ignorePlurals` 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) languages. To support this, you must place the CJK language **first**  **You should always specify a query 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/), or the languages you specified with the `ignorePlurals` or `removeStopWords` parameters. This can lead to 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/).
+      # Languages for language-specific query processing steps such as plurals, stop-word removal, and word-detection dictionaries  This setting sets a default list of languages used by the `removeStopWords` and `ignorePlurals` 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) languages. To support this, you must place the CJK language **first**  **You should always specify a query 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), or the languages you specified with the `ignorePlurals` or `removeStopWords` parameters. This can lead to 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).
       attr_accessor :query_languages
 
       # ISO language codes that adjust settings that are useful for processing natural language queries (as opposed to keyword searches) - Sets `removeStopWords` and `ignorePlurals` to the list of provided languages. - Sets `removeWordsIfNoResults` to `allOptional`. - Adds a `natural_language` attribute to `ruleContexts` and `analyticsTags`.
@@ -62,22 +62,22 @@ module Algolia
       # Assigns a rule context to the run query [Rule contexts](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/how-to/customize-search-results-by-platform/#whats-a-context) are strings that you can use to trigger matching rules.
       attr_accessor :rule_contexts
 
-      # Unique pseudonymous or anonymous user identifier.  This helps with analytics and click and conversion events. For more information, see [user token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken/).
+      # Unique pseudonymous or anonymous user identifier.  This helps with analytics and click and conversion events. For more information, see [user token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken).
       attr_accessor :user_token
 
-      # Whether to include a `queryID` attribute in the response The query ID is a unique identifier for a search query and is required for tracking [click and conversion events](https://www.algolia.com/guides/sending-events/getting-started/).
+      # Whether to include a `queryID` attribute in the response The query ID is a unique identifier for a search query and is required for tracking [click and conversion events](https://www.algolia.com/guides/sending-events/getting-started).
       attr_accessor :click_analytics
 
       # Whether this search will be included in Analytics.
       attr_accessor :analytics
 
-      # Tags to apply to the query for [segmenting analytics data](https://www.algolia.com/doc/guides/search-analytics/guides/segments/).
+      # Tags to apply to the query for [segmenting analytics data](https://www.algolia.com/doc/guides/search-analytics/guides/segments).
       attr_accessor :analytics_tags
 
       # Whether to enable index level A/B testing for this run request. If the composition mixes multiple indices, the A/B test is ignored.
       attr_accessor :enable_ab_test
 
-      # Whether this search will use [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking/) This setting only has an effect if you activated Dynamic Re-Ranking for this index in the Algolia dashboard.
+      # Whether this search will use [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking) This setting only has an effect if you activated Dynamic Re-Ranking for this index in the Algolia dashboard.
       attr_accessor :enable_re_ranking
 
       # A list of extenrally injected objectID groups into from an external source.
@@ -495,8 +495,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/personalization.rb

@@ -222,8 +222,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/range.rb

@@ -210,8 +210,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/redirect.rb

@@ -7,7 +7,7 @@ require "time"
 
 module Algolia
   module Composition
-    # [Redirect results to a URL](https://www.algolia.com/doc/guides/managing-results/rules/merchandising-and-promoting/how-to/redirects/), this this parameter is for internal use only.
+    # [Redirect results to a URL](https://www.algolia.com/doc/guides/managing-results/rules/merchandising-and-promoting/how-to/redirects), this this parameter is for internal use only.
     class Redirect
       attr_accessor :index
 
@@ -201,8 +201,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/redirect_rule_index_data.rb

@@ -204,8 +204,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/redirect_rule_index_metadata.rb

@@ -251,8 +251,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/redirect_url.rb

@@ -202,8 +202,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/remove_stop_words.rb

@@ -105,6 +105,5 @@ module Algolia
         end
       end
     end
-
   end
 end

data/lib/algolia/models/composition/rendering_content.rb

@@ -220,8 +220,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/request_body.rb

@@ -201,8 +201,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/results_composition_info_response.rb

@@ -205,8 +205,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/results_injected_item_applied_rules_info_response.rb

@@ -204,8 +204,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/results_injected_item_info_response.rb

@@ -214,8 +214,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/rules_batch_composition_action.rb

@@ -104,6 +104,5 @@ module Algolia
         end
       end
     end
-
   end
 end

data/lib/algolia/models/composition/rules_multiple_batch_request.rb

@@ -214,8 +214,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/rules_multiple_batch_response.rb

@@ -8,7 +8,7 @@ require "time"
 module Algolia
   module Composition
     class RulesMultipleBatchResponse
-      # Unique identifier of a task.  A successful API response means that a task was added to a queue. It might not run immediately. You can check the task's progress with the [`task` operation](#tag/Indices/operation/getTask) and this `taskID`.
+      # Unique identifier of a task.  A successful API response means that a task was added to a queue. It might not run immediately. You can check the task's progress with the [`task` operation](https://www.algolia.com/doc/rest-api/search/get-task) and this task ID.
       attr_accessor :task_id
 
       # Attribute mapping from ruby-style variable name to JSON key.
@@ -204,8 +204,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/search.rb

@@ -210,8 +210,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end

data/lib/algolia/models/composition/search_composition_rules_params.rb

@@ -17,10 +17,10 @@ module Algolia
       # Only return composition rules that match the context (exact match).
       attr_accessor :context
 
-      # Requested page of the API response.  Algolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/)).  - `hitsPerPage`: sets the number of search results (_hits_) displayed per page. - `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.  For example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.
+      # Requested page of the API response.  Algolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js)).  - `hitsPerPage`: sets the number of search results (_hits_) displayed per page. - `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.  For example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.
       attr_accessor :page
 
-      # Maximum number of hits per page.  Algolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/)).  - `hitsPerPage`: sets the number of search results (_hits_) displayed per page. - `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.  For example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.
+      # Maximum number of hits per page.  Algolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js)).  - `hitsPerPage`: sets the number of search results (_hits_) displayed per page. - `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.  For example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.
       attr_accessor :hits_per_page
 
       # If `true`, return only enabled composition rules. If `false`, return only inactive composition rules. By default, _all_ composition rules are returned.
@@ -254,8 +254,6 @@ module Algolia
           value
         end
       end
-
     end
-
   end
 end