Enum Mapper Laravel Package

Product Decisions This Supports

• Feature Development: Enables clean, type-safe enum handling in PHP/Laravel applications without database-level ENUM constraints, improving developer experience and reducing boilerplate.
• Roadmap Alignment: Accelerates implementation of feature flags, status systems (e.g., order states, user roles), or configuration-driven workflows where enums are critical.
• Build vs. Buy: Avoids reinventing enum logic (e.g., custom classes or database migrations) while maintaining flexibility for future schema changes.
• Use Cases:
  • Replacing raw integers/strings in models (e.g., status = 1 → status = UserStatus::ACTIVE).
  • Localization-friendly enums (e.g., translating UserStatus::PENDING to "Awaiting Review" in multiple languages).
  • Dynamic enums (e.g., plugin-based or admin-configurable options without DB schema updates).

When to Consider This Package

• Adopt if:
  • Your Laravel/PHP app uses enums frequently but avoids database ENUMs due to portability or legacy constraints.
  • You need runtime flexibility (e.g., adding/removing enum values without migrations).
  • Your team prioritizes developer ergonomics over micro-optimizations (e.g., database-level ENUM storage).
• Look elsewhere if:
  • You’re using PostgreSQL/MySQL ENUMs and want native type safety (this is a PHP-layer workaround).
  • Your enums are static and simple (e.g., binary flags like is_active), where a constant class suffices.
  • You need strict compile-time checks (consider PHP 8.1+ enum types or libraries like spatie/enum).
  • The package’s low stars/activity raise maintenance concerns (evaluate alternatives like myclabs/php-enum or ramsey/uuid).

How to Pitch It (Stakeholders)

For Executives: "This package lets us treat enums like first-class citizens in PHP—cleaner code, fewer bugs, and easier maintenance—without locking us into database-specific features. It’s a lightweight way to standardize options (e.g., user roles, order statuses) across the app, reducing tech debt and speeding up feature delivery."

For Engineering: "Instead of managing raw integers or strings for states (e.g., 1 = active), we’ll use UserStatus::ACTIVE with built-in validation and human-readable labels. It’s a drop-in replacement for ad-hoc enum logic, works with Laravel’s Eloquent, and supports dynamic values. Tradeoff: slightly more memory usage vs. database ENUMs, but gains flexibility and readability."