From 0ea5daeafe049349508830a343d4e5c89f0b67d2 Mon Sep 17 00:00:00 2001
From: mscherer <dereuromark@web.de>
Date: Wed, 18 Feb 2026 20:17:44 +0100
Subject: [PATCH] Docs: Improve validation providers section

- Add subsection documenting how to call provider methods directly
  (e.g., Validation::date()) within custom rules for OR logic
- Move closure validation rules to its own section for better organization

Refs cakephp/docs#8229
---
 docs/en/orm/validation.md | 25 ++++++++++++++++++++++++-
 1 file changed, 24 insertions(+), 1 deletion(-)

diff --git a/docs/en/orm/validation.md b/docs/en/orm/validation.md
index 587041d7aa..87a1dcc8d8 100644
--- a/docs/en/orm/validation.md
+++ b/docs/en/orm/validation.md
@@ -235,6 +235,29 @@ class UsersTable extends Table
 }
 ```
 
+### Using Provider Methods Directly
+
+In some cases, you may want to call provider methods directly within a custom
+validation rule. You can access a provider class using `getProvider()` and then
+call its methods statically. However, for the default `Validation` class, you
+can simply call its methods directly:
+
+```php
+use Cake\Validation\Validation;
+
+$validator->add('start_on', 'dateOrDatetime', [
+    'rule' => function ($value): bool {
+        return Validation::datetime($value) || Validation::date($value);
+    },
+    'message' => __('Must be a date or datetime'),
+]);
+```
+
+This approach is useful when you need to combine multiple validation rules with
+OR logic, which is not directly supported by the validator's fluent interface.
+
+## Using Closures as Validation Rules
+
 You can also use closures for validation rules:
 
 ```php
@@ -245,7 +268,7 @@ $validator->add('name', 'myRule', [
         }
 
         return 'Not a good value.';
-    }
+    },
 ]);
 ```