Laravel Hyrule Laravel Package

Product Decisions This Supports

• Build vs. buy/adopt: Informs whether to standardize complex Laravel validation on square/laravel-hyrule instead of maintaining bespoke validator classes or per-form validation logic.
• Roadmap and platform modernization: The 3.0.0 release adds Laravel 10 support, making the package viable for teams planning or completing a Laravel upgrade. This supports decisions about dependency upgrades, technical debt reduction, and framework alignment.
• Feature delivery for complex forms and APIs: Expanded support for prohibited_if/unless, exclude_if/unless/with/without, and missing_if/unless/with enables more expressive conditional validation for onboarding, checkout, KYC, admin configuration, eligibility flows, and multi-step forms.
• Product velocity vs. custom code: Teams can ship conditional validation behavior with less custom PHP, fewer one-off rules, and more consistent validation semantics across product surfaces.
• Risk and release management: As a major version, 3.0.0 should trigger an upgrade-impact review: confirm Laravel version constraints, scan for breaking changes beyond the release summary, and regression-test validation-heavy user journeys before rollout.

When to Consider This Package

Consider adopting or upgrading when:

• The product runs on Laravel 10 or is actively upgrading to it.
• Teams repeatedly need conditional validation rules such as “required unless,” “prohibited if,” “exclude with/without,” or “missing if/unless/with.”
• Engineering wants to reduce custom validator code and keep validation logic closer to Laravel’s native rule syntax.
• The organization accepts a small open-source dependency maintained under the Square GitHub organization and is willing to track major-version upgrades.
• Validation behavior is a meaningful part of product quality, compliance, onboarding, or checkout flows where inconsistent rules create user-facing errors.

Look elsewhere or defer when:

• The product is on an older Laravel version and cannot yet move to Laravel 10; remain on the compatible 2.x line until upgrade planning is complete.
• Validation needs are simple and fully covered by native Laravel rules; adding a dependency may not be justified.
• The team requires vendor-supported SLAs, formal security review, or long-term commercial maintenance guarantees.
• The product is not Laravel/PHP or has standardized on a different validation layer.
• A major upgrade cannot be regression-tested across validation-critical flows; inThat case, schedule the upgrade deliberately rather than bundling it into unrelated releases.

How to Pitch It (Stakeholders)

For executives: This package helps product and engineering ship complex form and API validation faster with less custom code. The new 3.0.0 release aligns it with Laravel 10 and adds more conditional validation rules, which supports platform modernization and reduces validation defects in high-value flows such as onboarding, checkout, and compliance. It is a small open-source dependency, but the major-version upgrade should be planned and tested like any framework-alignment change.

For engineering: square/laravel-hyrule provides a fluent way to define custom Laravel validation rules and now supports Laravel 10 plus additional conditional rules. The upgrade to 3.0.0 is a major release, so confirm version constraints, review the full changelog, and regression-test validation paths before adoption. The payoff is less bespoke validator code, more consistent rule definitions, and better coverage for conditional form behavior.