Yeah that's what I'm talking about. Used to be Rule interface in previous versions, now ValidationRule interface. Neither implementation is great imho.

📦 iamfarhad/validation 4.1.2

🇮🇷 Complete Laravel Persian validation package - Iranian national ID, mobile numbers, Shamsi dates, IBAN/Sheba, postal codes & more. Modern Laravel 10-12 support with both ValidationRule objects & ...

🔗 https://github.com/iamfarhad/validation

📦 iamfarhad/validation 4.1.1

🇮🇷 Complete Laravel Persian validation package - Iranian national ID, mobile numbers, Shamsi dates, IBAN/Sheba, postal codes & more. Modern Laravel 10-12 support with both ValidationRule objects & ...

🔗 https://github.com/iamfarhad/validation

I didn't love Laravel's deprecated Rule class, as it made building messages hard.

I don't love the new ValidationRule because while messaging is now easy, this bare Closure requires a lot of inline logic in the validate() message and there's not a great way to break execution.

Statamic 4.51 brings with it support for Laravel's ValidationRule. It's time to write your own reusable rules for your Statamic Blueprints.

Find out more:
www.martyfriedel.com/blog/how-to-...

Want control over automations?

Use Custom Settings/Permissions to temporarily bypass Flows, Apex Triggers, and Validation Rules

buff.ly/PrE1HKA

#Salesforce #AwesomeAdmin #SalesforceAdmin #Trailblazer #TrailblazerCommunity #Apex #Flow #ValidationRule