Enumhancer Ide Helper Laravel Package

Product Decisions This Supports

• Developer Productivity: Accelerates PHP/Laravel development by reducing boilerplate for enums (e.g., getDescription(), isValid(), toArray()). Aligns with roadmap items targeting IDE tooling or developer experience (DX).
• Build vs. Buy: Justifies buying (open-source) over building custom enum utilities, especially for teams already using Laravel/PHP. Reduces technical debt in shared utility layers.
• Use Cases:
  • Teams migrating legacy codebases to modern PHP enums (PHP 8.1+).
  • Projects requiring strict type safety with human-readable enum values (e.g., payment statuses, user roles).
  • Internal tools or platforms where enums are heavily used (e.g., config management, workflow states).
• Roadmap Alignment: Supports initiatives to standardize code patterns (e.g., "Reduce IDE friction" or "Improve onboarding for new devs").

When to Consider This Package

• Adopt if:

  • Your team uses Laravel/PHP 8.1+ and enums are a core part of your domain model (e.g., >50 enum classes).
  • You prioritize developer velocity over minimal dependencies (AGPL-3.0 is acceptable for internal tools).
  • Your IDE (PHPStorm, VSCode) lacks native enum autocomplete/validation for custom methods (e.g., getDescription()).
  • You’re not constrained by AGPL-3.0 licensing (e.g., open-source projects or internal tools).

• Look elsewhere if:

  • Your codebase uses pre-PHP 8.1 or avoids enums entirely.
  • You need enterprise support or commercial licensing (AGPL-3.0 may require compliance review).
  • Your team prefers zero-dependency solutions or has existing enum libraries (e.g., Spatie’s laravel-enum).
  • The package’s lack of stars/maintenance (last release in 2023) is a blocker (mitigate with forks or internal forks).

How to Pitch It (Stakeholders)

For Executives: "This package cuts enum-related dev time by 30%+ by auto-generating IDE-friendly methods (e.g., descriptions, validation) for Laravel enums. For teams using enums heavily—like our [X] system—it’s a low-risk way to standardize code patterns without hiring or custom dev work. The AGPL license is fine for internal tools, and the maintenance burden is minimal since it’s a one-time setup."

For Engineering: *"Enumhancer adds zero runtime overhead but gives us:

• IDE autocomplete for custom enum methods (e.g., UserRole::ADMIN->getDescription()).
• Consistent patterns across the codebase (no more ad-hoc toArray() implementations).
• Future-proofing for PHP 8.1+ enums with minimal refactoring. Tradeoff: AGPL-3.0 (okay for [internal/open-source]), and we’d need to test it against our existing enum usage. Let’s prototype it in [Module Y] first."*

For Developers: *"Imagine writing enum UserRole { case ADMIN = 'admin'; } and instantly getting:

• ADMIN->description() → "Administrator"
• ADMIN->isValid() → true
• Autocomplete in PHPStorm for all methods. No more copy-pasting getDescription() logic. Let’s try it in [Feature Z] and compare to our current approach."*