Filament Input Select Affix Laravel Package

Product Decisions This Supports

• Unblocks the Laravel 12 upgrade path. Until 0.3.0, this package pinned us (or would have pinned us) below Laravel 12. If it is in the dependency tree, this release removes a hard blocker on a framework upgrade — that is a roadmap-level decision, not a cosmetic one. Confirm the constraint in composer.json was actually widened before treating the upgrade as cleared.
• Build vs. buy for styled select inputs. The package exists to give Filament's native Select prefix/suffix ("affix") support — currency symbols, units, domain suffixes, icons — that core Filament does not ship. The build alternative is a custom Filament field or a Blade view override. Buying costs a pre-1.0 dependency; building costs maintenance of a field that must track Filament's own major-version churn (v3 → v4 is on the horizon).
• Feature scoping for admin panels. If a spec says "amount field with a currency prefix" or "subdomain field with .example.com suffix," this package is the cheapest way to satisfy it without bespoke form code. Useful for finance, pricing, and settings screens in Filament admin panels.
• Cosmetic-affordance budget. Affixes are presentation, not behavior. They do not add validation, formatting, or data transformation. Scope decisions should not assume the package handles currency masking or unit conversion — it does not.
• Upgrade cadence signal. The release history is dominated by Dependabot bumps plus one community-submitted compatibility PR (via Laravel Shift). That tells you maintenance is reactive but functioning: someone else drives the compatibility work. Factor that into how much of the admin surface you want to depend on it.

When to Consider This Package

Adopt when:

• You are on Filament v3+ and need prefix/suffix decoration on select inputs, and a custom field would be disproportionate effort.
• You are on Laravel 12 (or moving to it) and the 0.3.0 constraint widening is what makes the dependency viable at all.
• The UI requirement is genuinely decorative — you can live with the package's rendering and do not need validation, formatting, or masking built in.
• You can tolerate a pre-1.0 dependency from a single maintainer in a non-critical path (admin UI, not customer-facing checkout).

Look elsewhere when:

• You need currency/number masking or input normalization — reach for a dedicated money or masked-input package instead, or pair this with server-side validation and a formatter.
• You are on Filament v4 or planning it soon. No evidence in this release of v4 readiness; the Laravel 12 PR is a framework-compatibility change, not a Filament major-version one. Verify before committing.
• Your dependency policy forbids 0.x versions or single-maintainer packages in production paths.
• The affix need is one-off — a single Blade view override is lower total cost than a lifetime dependency.
• You need vendor SLAs, security response commitments, or a support contract.

Before adopting, verify: the actual composer.json constraints for laravel/framework and filament/filament, whether tests run against Laravel 12 in CI, and whether the maintainer has signalled a 1.0 timeline.

How to Pitch It (Stakeholders)

To executives: This is a small, free plugin that decorates dropdown fields in our admin panel with prefixes and suffixes — currency symbols, units, domain endings. The 0.3.0 release is a compatibility release: it adds Laravel 12 support, which matters because it clears a blocker on our framework upgrade. No new features, no breaking changes, no cost. Risk is proportionate to scope — it is a presentation-layer admin dependency from a single maintainer, so we keep it out of customer-facing and revenue-critical surfaces.

To engineering: 0.3.0 is Laravel 12 compatibility (community PR via Laravel Shift) plus routine CI dependency bumps. Nothing breaking, nothing new to learn. Two asks: (1) confirm the framework constraint in composer.json is genuinely widened and that CI exercises Laravel 12, and (2) confirm Filament v4 posture before we schedule that upgrade, because this release says nothing about it. Treat the package as pre-1.0 and pin it; do not let it drift onto a critical path.

Recommendation: keep, upgrade, and re-evaluate at the next Filament major or if the maintainer goes quiet for more than two Laravel release cycles.