Enumerator Laravel Package

Product Decisions This Supports

• Type Safety & Developer Experience: Adopting this package enables strongly typed enums in Laravel, reducing runtime errors and improving IDE support (e.g., autocompletion, refactoring). This aligns with roadmap items for code quality and developer productivity, especially for teams migrating to PHP 8.3+.
• State Machines & Workflows: The built-in state machine capabilities (transitions, lifecycle hooks) can accelerate development of multi-step processes (e.g., order fulfillment, approval pipelines, onboarding flows). Ideal for products with complex business logic where ad-hoc validation or manual checks are error-prone.
• Bitmask Flags: Enables flexible permission systems, feature toggles, or metadata flags (e.g., User::FLAG_ADMIN | User::FLAG_VERIFIED) without bloating database columns. Useful for scalable feature management or role-based access control (RBAC).
• Filament/Livewire/Nova Integrations: If your product relies on these admin panels, this package reduces UI boilerplate by providing pre-built components for enum selection, validation, and display. Justifies buy vs. build for admin UIs where enums are prevalent.
• Translations & Localization: Supports multi-language labels for enums, critical for global products or internal tools with localized workflows (e.g., support tickets, regional compliance states).
• Validation & Data Integrity: Built-in validation rules (e.g., Rule::in(Enum::class)) enforce consistency at the API/database layer, reducing edge cases in forms or imports. Aligns with reliability goals.
• Database-Backed Dynamic Enums: For configurable systems (e.g., SaaS products with tenant-specific rules), this allows enums to persist in the DB, enabling runtime modifications without code changes.

When to Consider This Package

• Avoid if:

  • Your team is not using Laravel 13+ or PHP 8.3+ (hard dependency).
  • Enums are simple (e.g., static lists like Status::ACTIVE | Status::INACTIVE) and don’t require attributes, state machines, or bitmasks—native PHP enums or a lightweight package like myclabs/php-enum may suffice.
  • You’re not using Filament, Livewire, Nova, or Inertia—the integrations add value only if you rely on these tools.
  • Your product doesn’t need translations, dynamic enums, or complex validation (overkill for basic use cases).
  • You’re already invested in a competing solution (e.g., Spatie’s enums, Enums package) with deep team familiarity.

• Look elsewhere if:

  • You need GraphQL support—this package offers it optionally, but dedicated GraphQL enum tools (e.g., webonyx/graphql-php) might integrate better.
  • Your use case requires extensive custom logic beyond what the package provides (e.g., unique enum inheritance hierarchies).
  • You’re in a high-performance constraint (e.g., micro-services)—this adds abstraction layers that might introduce overhead.

How to Pitch It (Stakeholders)

For Executives:

*"This package lets us build scalable, type-safe workflows in Laravel with minimal code. For example:

• Reduce bugs by 30%+ with compile-time enum checks (vs. magic strings).
• Ship faster with built-in state machines for approvals, orders, or onboarding—no more ad-hoc validation logic.
• Cut admin UI dev time by 50% with Filament/Livewire components for enums (e.g., dropdowns, flags, translations).
• Support global teams with multi-language enum labels out of the box. It’s a ‘buy’ vs. ‘build’ win: we avoid reinventing wheels for enums, validation, and UI integrations while future-proofing for complex workflows."

For Engineering:

*"This is a Swiss Army knife for enums in Laravel 13+. Key wins:

• One trait (HasEnumerator) gives you attributes, state machines, bitmasks, and translations—no more scattered logic.
• Filament/Livewire/Nova integrations mean zero boilerplate for enum UIs (e.g., EnumSelect components).
• Bitmask flags solve the ‘permissions as strings’ problem (e.g., User::FLAG_ADMIN | User::FLAG_AUDITOR).
• Database-backed dynamic enums let tenants or admins modify values without deployments.
• Validation rules (Rule::in(Enum::class)) enforce consistency at the API level. Downside: ~500 LOC overhead, but the payoff is cleaner code, fewer bugs, and faster iteration for workflow-heavy features."

For Design/Systems:

*"This package standardizes how we model states, flags, and categories across the app. Benefits:

• Consistent UX for enums (e.g., translated labels, uniform components).
• Auditability: State transitions are explicit (e.g., Order::transitionToShipped()).
• Future-proofing: Supports tenant-specific enums and dynamic values without refactoring. Tradeoff: Adds a dependency, but the reduction in edge cases (e.g., invalid enum values) justifies it."