Doctrine Types Bundle Laravel Package

Product Decisions This Supports

• Compliance Expansion: Enables support for Spanish tax identifiers (NIF) and other regional validations (e.g., Belgian enterprise numbers, IBAN, SIRET), critical for EU-focused SaaS platforms, fintech, or e-commerce targeting Spain/Belgium. Reduces custom validation logic and legal risks.
• Build vs. Buy: Justifies outsourcing validation logic for niche types (e.g., SpanishNif, BelgianEnterpriseNumber) instead of maintaining custom Doctrine types, saving ~30–50% development time per locale.
• Roadmap Alignment: PHP 8.4+ requirement forces infrastructure upgrades, aligning with Laravel 10+ (released Nov 2023) and reducing legacy PHP debt for long-term projects.
• Global Scalability: Pre-built types for money, currencies, IBANs, and postal codes accelerate multi-country feature rollouts (e.g., EU-wide payment processing).
• Risk Mitigation: Proactive PHP version drops (e.g., PHP < 8.4) and CI/CD improvements (PHPUnit 10, Rector) reduce security vulnerabilities and technical debt in production.

When to Consider This Package

• Adopt When:

  • Your product requires Spanish/Belgian/EU compliance (e.g., NIF, SIRET, IBAN validation) and you want to avoid custom implementations.
  • You’re upgrading to PHP 8.4+ and need maintained Doctrine types that support modern PHP features (e.g., attributes, typed properties).
  • Your team prioritizes developer velocity over custom validation logic, especially for repetitive regional formats (e.g., phone numbers, postal codes).
  • You’re building for multi-country EU markets and need standardized validation for tax IDs, currencies, and financial data.
  • You want to reduce technical debt by adopting a batteries-included solution with active maintenance (monthly releases, PHPUnit 10).

• Look Elsewhere If:

  • You’re stuck on PHP < 8.4 (this bundle drops support for older versions).
  • Your use case requires types not covered (e.g., NIE for Spanish foreigners, or domain-specific formats like US SSN).
  • You need native Laravel Eloquent integration (this is Doctrine-first; requires laravel-doctrine or manual bridges).
  • Your project doesn’t use Doctrine ORM/DBAL (core limitation).
  • You rely on Symfony’s validator and can’t translate constraints to Laravel’s Validator (requires custom adapters).
  • You’re in a highly regulated industry (e.g., healthcare) where auditability of custom validation is critical.

How to Pitch It (Stakeholders)

For Executives: *"This bundle eliminates custom validation work for Spanish tax IDs (NIF), Belgian enterprise numbers, and other EU-specific formats—critical for our expansion into Spain and Belgium. By adopting it, we:

• Cut development time by 40% for compliance-heavy features.
• Future-proof our stack with PHP 8.4+ support, aligning with Laravel 10+.
• Reduce legal risks with pre-validated types for IBANs, SIRENs, and currencies. It’s a low-risk, high-reward investment for scaling into regulated markets."

For Engineers: *"Key wins in v2.16.0:

• New SpanishNifType: Validates Spanish tax IDs out of the box—no more reinventing NIF rules.
• PHP 8.4+ mandate: Drops legacy support to force modernization (great for Laravel 10+).
• PHP 8.5 in tests: Early compatibility for future upgrades.
• CI/CD upgrades: PHPUnit 10 and Rector mean fewer flaky tests and cleaner code. Perfect for teams needing scalable, validated types for Spain/EU or looking to upgrade PHP without custom Doctrine overhead."

For Architects: *"This bundle strengthens our EU compliance toolkit with SpanishNifType and BelgianEnterpriseNumber, while the PHP 8.4+ requirement aligns with our Laravel 10+ roadmap. Trade-offs:

• Gain: Reduced maintenance for regional validations, future-proofing, and enterprise-grade testing.
• Loss: Slightly higher entry barrier for PHP < 8.4 teams (but worth it for most modern stacks). Ideal for payment processing, multi-tenant SaaS, or regulated industries where compliance and scalability are priorities."

For PMs: *"This solves three critical pain points:

1. Compliance: Pre-built validation for Spain/Belgium reduces legal risks.
2. Speed: Saves months of dev time on custom Doctrine types.
3. Future-proofing: PHP 8.4+ alignment avoids tech debt. Prioritize this if you’re expanding into Europe or need to modernize your PHP stack."