Enumhancer Laravel Package

Product Decisions This Supports

• Adoption of PHP 8.1+ enums: Justify migrating legacy codebases to native enums by offering a robust, framework-agnostic toolkit to reduce friction.
• Type safety & maintainability: Push for stricter type enforcement in Laravel applications by replacing ad-hoc string constants or Spatie’s enums with a standardized, enhanced enum system.
• Developer productivity: Accelerate feature development by reducing boilerplate (e.g., serialization, validation, or localization of enums) and enabling reusable, self-documenting code.
• Framework-agnostic roadmap: Future-proof Laravel projects by avoiding vendor lock-in (e.g., Spatie’s Laravel-specific enums) while maintaining compatibility with existing Spatie-based codebases.
• Build vs. buy: Replace custom enum utilities or partial solutions (e.g., handwritten serialization logic) with a maintained, battle-tested package.
• Use cases:
  • Domain modeling: Define immutable, self-validating business entities (e.g., OrderStatus, PaymentMethod).
  • API contracts: Standardize request/response payloads (e.g., HttpStatus, ErrorCode).
  • Configuration: Manage app-wide settings (e.g., FeatureFlags, LogLevels) with runtime safety.
  • Localization/i18n: Attach human-readable labels to enums without coupling to Laravel’s localization systems.

When to Consider This Package

• Adopt if:

  • Your team is using PHP 8.1+ and wants to leverage native enums without framework-specific constraints.
  • You need case-insensitive enums to avoid naming collisions (e.g., UserRole vs. USER_ROLE).
  • You’re migrating from Spatie’s PHP Enum (or similar) to native enums and want backward compatibility.
  • Your project requires type-agnostic enums (no need for BackedEnum complexity) but still needs advanced features like serialization, validation, or localization.
  • You’re building a Laravel-agnostic library or microservice where framework-specific tools (e.g., Spatie’s Laravel package) are incompatible.
  • You prioritize maintainability over minimalism and want built-in support for common enum operations (e.g., filtering, mapping, or database storage).

• Look elsewhere if:

  • You’re locked into PHP < 8.1 or need legacy support.
  • Your use case is Laravel-specific (e.g., Eloquent model enums) and Spatie’s Laravel package already fits your needs.
  • You require PHPUnit assertion methods (not yet supported in this package).
  • You prefer minimal dependencies and can implement enum logic manually (e.g., simple enums with no extra features).
  • Your team lacks PHP 8.1+ expertise or needs active community support (this package has low dependents/stars).
  • You’re using Symfony or another framework with built-in enum tools (e.g., Symfony’s Enum component).

How to Pitch It (Stakeholders)

For Executives/Stakeholders

"Enumhancer is a strategic investment to modernize our PHP codebase with native enums—reducing bugs, improving type safety, and cutting development time. By adopting this framework-agnostic toolkit, we can:

• Future-proof our Laravel apps by avoiding vendor lock-in while maintaining compatibility with existing Spatie-based code.
• Accelerate feature delivery with built-in enum validation, serialization, and localization, eliminating repetitive boilerplate.
• Enhance maintainability by replacing ad-hoc string constants or custom enum logic with a standardized, self-documenting system.
• Simplify migrations from legacy enums to PHP 8.1+ with backward-compatible tools.

This aligns with our tech debt reduction goals and sets us up for scalable, type-safe development—without framework limitations."

For Engineering Teams

"Enumhancer solves critical pain points for PHP 8.1+ enums in Laravel (and beyond):

• Case-insensitive enums: No more Enum vs. ENUM collisions.
• Type-agnostic flexibility: Avoid BackedEnum overhead unless needed.
• Built-in utilities: Serialization (JSON/DB), validation, localization, and more—out of the box.
• Spatie migration path: Seamlessly transition from Spatie’s PHP Enum to native enums with minimal refactoring.
• Framework-agnostic: Works in Laravel, Symfony, or standalone PHP—no lock-in.

For teams using PHP 8.1+, this reduces cognitive load, improves code quality, and future-proofs our enum strategy. Let’s pilot it in [Module X] to validate the ROI before broader adoption."

Key Risk Mitigation:

• Start with a non-critical module to test integration and developer adoption.
• Compare performance overhead vs. custom solutions (benchmarks provided in the README).
• Highlight backward compatibility with Spatie’s enums to ease migration.