fix(specs): condition cant be numeric filter (#4726) (generated) [skip ci]

Co-authored-by: Kai Welke <[email protected]>
Co-authored-by: Pierre Millot <[email protected]>

Author: 3 people

clients/algoliasearch-client-csharp/algoliasearch/Models/Search/Condition.cs

@@ -51,9 +51,9 @@ public Condition()
   public string Context { get; set; }
 
   /// <summary>
-  /// Filters that trigger the rule.  You can add 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. 
+  /// 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. 
   /// </summary>
-  /// <value>Filters that trigger the rule.  You can add 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. </value>
+  /// <value>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. </value>
   [JsonPropertyName("filters")]
   public string Filters { get; set; }
 

clients/algoliasearch-client-dart/packages/client_search/lib/src/model/condition.dart

@@ -32,7 +32,7 @@ final class Condition {
   @JsonKey(name: r'context')
   final String? context;
 
-  /// Filters that trigger the rule.  You can add 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.
+  /// 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.
   @JsonKey(name: r'filters')
   final String? filters;
 

clients/algoliasearch-client-go/algolia/search/model_condition.go

@@ -85,9 +85,10 @@ public Condition setFilters(String filters) {
   }
 
   /**
-   * Filters that trigger the rule. You can add 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.
+   * 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.
    */
   @javax.annotation.Nullable
   public String getFilters() {

clients/algoliasearch-client-java/algoliasearch/src/main/java/com/algolia/model/search/Condition.java

@@ -21,7 +21,7 @@ export type Condition = {
   context?: string;
 
   /**
-   * Filters that trigger the rule.  You can add 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.
+   * 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.
    */
   filters?: string;
 };

clients/algoliasearch-client-javascript/packages/client-search/model/condition.ts

@@ -11,7 +11,7 @@ import kotlinx.serialization.json.*
  * @param anchoring
  * @param alternatives Whether the pattern should match plurals, synonyms, and typos.
  * @param context 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.
- * @param filters Filters that trigger the rule.  You can add 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.
+ * @param filters 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.
  */
 @Serializable
 public data class Condition(
@@ -27,6 +27,6 @@ public data class Condition(
   /** 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.  */
   @SerialName(value = "context") val context: String? = null,
 
-  /** Filters that trigger the rule.  You can add 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.  */
+  /** 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.  */
   @SerialName(value = "filters") val filters: String? = null,
 )

clients/algoliasearch-client-kotlin/client/src/commonMain/kotlin/com/algolia/client/model/search/Condition.kt

@@ -292,7 +292,7 @@ public function getFilters()
     /**
      * Sets filters.
      *
-     * @param null|string $filters Filters that trigger the rule.  You can add 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.
+     * @param null|string $filters 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.
      *
      * @return self
      */

clients/algoliasearch-client-php/lib/Model/Search/Condition.php

@@ -47,7 +47,7 @@ class Condition(BaseModel):
     context: Optional[str] = None
     """ 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.  """
     filters: Optional[str] = None
-    """ Filters that trigger the rule.  You can add 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.  """
+    """ 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.  """
 
     @field_validator("context")
     def context_validate_regular_expression(cls, value):

clients/algoliasearch-client-python/algoliasearch/search/models/condition.py

@@ -19,7 +19,7 @@ class Condition
       # 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.
       attr_accessor :context
 
-      # Filters that trigger the rule.  You can add 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.
+      # 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.
       attr_accessor :filters
 
       # Attribute mapping from ruby-style variable name to JSON key.

clients/algoliasearch-client-ruby/lib/algolia/models/search/condition.rb

@@ -49,9 +49,9 @@ import algoliasearch.search.Anchoring._
   *   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.
   * @param filters
-  *   Filters that trigger the rule. You can add 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.
+  *   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.
   */
 case class Condition(
     pattern: Option[String] = scala.None,

clients/algoliasearch-client-scala/src/main/scala/algoliasearch/search/Condition.scala

@@ -19,9 +19,9 @@ public struct SearchCondition: Codable, JSONEncodable {
     /// 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.
     public var context: String?
-    /// Filters that trigger the rule.  You can add add filters using the syntax `facet:value` so that the rule is
+    /// 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.
+    /// `pattern` parameter. You can't combine multiple filters with `OR` and you can't use numeric filters.
     public var filters: String?
 
     public init(

clients/algoliasearch-client-swift/Sources/Search/Models/SearchCondition.swift

@@ -22433,11 +22433,14 @@ components:
             Filters that trigger the rule.
 
 
-            You can add add filters using the syntax `facet:value` so that the
-            rule is triggered, when the specific filter is selected.
+            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.
           example: genre:comedy
     editType:
       description: Type of edit.

docs/bundled/search.yml

@@ -7242,11 +7242,14 @@ components:
             Filters that trigger the rule.
 
 
-            You can add add filters using the syntax `facet:value` so that the
-            rule is triggered, when the specific filter is selected.
+            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.
           example: genre:comedy
     editType:
       description: Type of edit.