Consistence Bundle Laravel Package

Product Decisions This Supports

• Feature scoping for enum-driven UI: This package exists to render PHP enums as form choices and translate their labels. If your roadmap includes status pickers, role selectors, order-state filters, or admin filters backed by enums, this is the exact problem space it addresses — but only on Symfony's Form component.
• Build vs. buy for presentation glue: The package is a thin integration layer (one form type + one translator) over consistence/consistence. For a Laravel codebase, the equivalent is ~50–100 lines (a Blade component or a Rule::enum + __() label map). The build-vs-buy answer is almost certainly build in Laravel and buy (i.e., install) only in a Symfony/Consistence-heavy stack.
• Localization roadmap: It supports translated enum labels out of the box, which is a real PM-level decision — do you ship one canonical label per enum case, or per-locale labels? This package assumes per-locale translation keys, which affects content-ops workflow and translation-file ownership.
• Framework standardization: Adopting it signals a commitment to consistence/consistence enums over native PHP 8.1 backed enums. That is a strategic decision about domain modeling, not just UI — it touches validation, persistence (Doctrine mapping), and API serialization.
• Risk budgeting: Stars (1), dependents (0), and the low opportunity score (17.5) mean this is a low-signal, low-adoption package. A PM decision here is less "should we use this?" and more "do we want to depend on an unmaintained integration for UI plumbing?"

When to Consider This Package

Consider it only when all of the following hold:

• You are on Symfony (this is a bundle), not Laravel — the Laravel framing does not apply, and there is no Laravel service provider or facade here.
• You already use consistence/consistence enums in your domain layer and want Symfony EnumType form elements plus translator integration without writing glue.
• You have a small, contained admin surface where the cost of vendoring or forking a 1-star package is acceptable.
• You are comfortable pinning the version and accepting that upstream maintenance may be sporadic.

Look elsewhere (or build in-house) when:

• You are on Laravel — native PHP 8.1 backed enums, Rule::enum, Blade @foreach, and __() label maps cover this with zero third-party risk.
• You use native backed enums rather than Consistence enums; this package gives you nothing.
• You need active maintenance, security responsiveness, or a community to lean on — 0 dependents is a strong signal of abandonment risk.
• You need richer enum UI (searchable selects, dependent dropdowns, API-driven option lists) — a form type + translator is a floor, not a ceiling.
• You require API/serialization translation (JSON:API, GraphQL enum descriptions); this targets server-rendered forms.

How to Pitch It (Stakeholders)

Executive summary: This is a small Symfony bundle that turns PHP enums into translatable form dropdowns. It solves a real but narrow problem — consistent, localized enum labels in admin and back-office forms — and it does so with minimal code.

Recommendation: Treat it as a reference implementation, not a dependency. For a Laravel product, we should not adopt it: the framework mismatch is total, the package has negligible adoption (1 star, 0 dependents), and the functionality is trivially reproducible with native enums plus a label translation map. For a Symfony product already standardized on Consistence enums, it is a low-effort convenience worth evaluating in a spike, with a fork-and-vendor fallback documented.

What it costs us: MIT license, no commercial lock-in, but also no support contract. The real cost is the risk of an unmaintained dependency in UI plumbing and the coupling of our domain enums to a specific library's enum abstraction.

What we get: A repeatable pattern for localized enum labels, faster delivery of admin filters and status selectors, and a clear precedent for how we model enum-to-UI translation across the product. Even if we don't install it, the pattern is worth copying into an internal helper — which gives us the benefit with none of the dependency risk.