Better Types Laravel Package

Product Decisions This Supports

• Type Safety & Developer Experience (DX):

  • Enables stricter type validation in Laravel/PHP applications, reducing runtime errors and improving maintainability.
  • Supports union types (e.g., string|int) and named types (e.g., custom classes), aligning with modern PHP 8+ features.
  • Useful for APIs, form validation, and data processing where input validation is critical.

• Build vs. Buy:

  • Buy: Avoid reinventing type-checking logic (e.g., manual instanceof checks or regex validation).
  • Build: Only if needing highly customized type logic (e.g., domain-specific constraints).

• Roadmap Priorities:

  • Phase 1: Integrate into core validation layers (e.g., Laravel’s FormRequest or API gateways).
  • Phase 2: Extend to serialization/deserialization (e.g., JSON API payloads) or event dispatching.
  • Phase 3: Explore IDE integration (e.g., PhpStorm hints) for proactive type safety.

• Use Cases:

  • APIs: Validate incoming requests (e.g., Accepts: User|Admin).
  • Forms: Enforce type constraints (e.g., Email|PhoneNumber).
  • Legacy Systems: Gradually introduce type safety without full refactoring.

When to Consider This Package

• Adopt if:

  • Your team uses PHP 8+ and wants to leverage union/named types without verbose checks.
  • You’re building scalable APIs or data pipelines where input validation is critical.
  • You prioritize developer productivity (reduces boilerplate for type validation).
  • Your stack includes Laravel (seamless integration with existing validation tools).

• Look elsewhere if:

  • You’re on PHP < 8.0 (package requires PHP 8+ features).
  • Your type needs are trivial (e.g., only basic string|int checks).
  • You need runtime performance optimization (this adds minimal overhead but isn’t a micro-optimization tool).
  • Your team lacks PHP 8+ adoption or type-hinting culture.

How to Pitch It (Stakeholders)

For Executives: "This package lets us enforce stricter type rules in our PHP/Laravel apps—catching bugs early and reducing runtime errors. It’s like adding a ‘compile-time guardrail’ for data validation, which cuts debugging time and improves API/form reliability. Low risk (MIT license, battle-tested by Spatie), high reward for developer productivity."

For Engineers: *"Spatie’s better-types gives us a clean way to validate union/named types (e.g., User|Admin or custom classes) without manual instanceof spaghetti. Works seamlessly with Laravel’s validation, and the syntax is intuitive:

if (BetterType::isType($input, User::class | Admin::class)) { ... }

It’s a drop-in upgrade for type safety—no refactoring needed. Perfect for APIs, forms, or legacy systems where we want to modernize validation."*