Laravel Validation Laravel Package

Product Decisions This Supports

• Build vs. buy for niche validation: v4.0.1 confirms active maintenance of domain-specific rules (hetu, portuguese_nif, public_domain_suffix, mimetype, uploaded, contains_count, between_exclusive). Adopting the package avoids hand-rolling error-prone validators for tax IDs, national identity codes, file types, and domain suffixes. The patch release lowers the “abandoned dependency” risk that would otherwise favor a build.
• Internationalization / market-entry roadmap: The release adds en and pt_BR messages for 7 rules that previously surfaced raw translation keys (e.g., validation.hetu) to end users. This directly supports launches or growth in Portuguese-speaking markets and improves English-language UX. Localization coverage is a gating item for i18n milestones; this release closes a visible gap.
• Customer-facing quality of validation errors: Raw key leakage is a polish/QA defect that erodes trust in KYC, onboarding, and upload flows. The fix means product teams can ship these rules without adding custom translation overrides. This removes a recurring “translation debt” item from the backlog.
• Feature scope decisions: The documented placeholder parameter mapping (:value, :values, :min, :max) reduces support load and enables product/design to author precise error copy per rule without reverse-engineering the library. Useful for content and UX writing decisions.
• Upgrade/roadmap safety: v4.0.1 is a patch release with no breaking changes. Post-4.0 API stability is a positive signal for planning adoption in the next quarter rather than deferring. The removal of the unused attribute message is low risk but should be verified against any custom translation overrides.

When to Consider This Package

Adopt when:

• You are building on Laravel and need the specific rules this package provides (hetu, portuguese_nif, public_domain_suffix, mimetype, uploaded, contains_count, between_exclusive) rather than generic core validation.
• You need localized error messages in en or pt_BR for those rules; v4.0.1 makes them human-readable out of the box.
• You want to avoid maintaining custom Respect Validation integrations and rule-specific translation files.
• You are on a supported Laravel/PHP version and want a low-risk, patch-level dependency addition.
• You value documented placeholder semantics for building custom messages or dynamic error copy.

Look elsewhere or proceed cautiously when:

• You only need standard Laravel validation rules — this package adds no value and adds a dependency.
• You require broad locale coverage beyond en and pt_BR; other locales will still surface raw keys for these rules, requiring your own translation work.
• You are on an unsupported Laravel/PHP version or need a commercially supported package with an SLA.
• Compliance/audit requirements mandate in-house ownership of sensitive validators (e.g., hetu, portuguese_nif); evaluate whether OSS governance meets your review bar.
• You have custom translation overrides that referenced the now-removed attribute message — verify before upgrading (low likelihood, but check).

How to Pitch It (Stakeholders)

Executive summary: This is a small, actively maintained open-source Laravel package that supplies specialized validation rules (tax IDs, national identity codes, file types, domain suffixes) plus localized English and Brazilian Portuguese error messages. The v4.0.1 release is a maintenance patch: it fixes raw error keys for seven rules, removes dead code, and improves documentation. Adopting it is a low-cost alternative to building and maintaining these validators in-house, with no breaking changes in this release.

Engineering summary: v4.0.1 fixes missing en and pt_BR messages for between_exclusive, contains_count, hetu, mimetype, portuguese_nif, public_domain_suffix, and uploaded; removes the unused attribute message because Laravel’s validateAttribute() shadows the Respect rule; and documents placeholder parameter usage. Upgrade path is a patch bump. Run the test suite, spot-check translation overrides for the removed attribute key, and verify error output in both locales. No API changes expected.

Product/Design summary: End users in English and Brazilian Portuguese locales will now see readable validation errors instead of raw keys like validation.hetu. This improves form UX for onboarding, KYC, and file-upload flows without requiring design or copy changes — and it removes a custom translation workaround from the backlog.