Fin Modal Table Select Laravel Package

Product Decisions This Supports

• Feature delivery for Filament admin panels: This package supplies a modal-based table selector form component, which unblocks common record-picking workflows (attach a record, choose a related entity, pick from a report, assign coverage, etc.) without bespoke Livewire modal code.
• Build vs buy: A narrow, single-purpose UI primitive like this is almost always a "buy/adopt" rather than "build." The v1.1.4 note shows an external user reporting a real defect and the maintainer shipping a targeted fix — evidence of a maintained dependency rather than an abandoned one.
• Use-case coverage decisions: The package supports two distinct modes — standalone selection and relationship-scoped tables — plus array-backed tables. That combination matters for roadmap items involving non-Eloquent data sources (dashboards, imported/reporting rows, computed datasets) where a standard relationship select would not work.
• Record action integration: The fix specifically covers opening the picker from a table record action. This supports roadmap decisions around row-level actions opening embedded forms, which is a common pattern for attach/assign/coverage flows.
• Risk posture for upgrades: v1.1.4 is a patch release with no breaking changes, so it can be adopted inside a normal maintenance window without a migration plan or stakeholder sign-off beyond routine QA.

When to Consider This Package

Consider adopting when:

• The application is on Laravel + Filament and needs a searchable, modal-based record picker as a form field.
• You need both relationship-scoped selection and standalone selection from the same component, rather than maintaining two implementations.
• You have array-backed or otherwise non-Eloquent tables and want record actions to open a picker (the exact scenario fixed in v1.1.4).
• You want a small, focused dependency instead of a custom Livewire modal with its own state, authorization, and search logic.
• You value an actively maintained dependency: the release references a community-reported issue and a fast, scoped patch.

Look elsewhere or build in-house when:

• You are not on Filament, or you are on a Filament major version this package does not track.
• Your selection needs are heavily bespoke — complex multi-tenant authorization, custom search backends, or selection across heterogeneous sources that the component's scoping model does not express.
• You need a first-party-supported component with a guaranteed support window; this is a small third-party package with a correspondingly small maintenance surface.
• The picker is a peripheral convenience rather than a core workflow — the cost of owning a small custom implementation may be lower than tracking a dependency.
• Caveat on evidence: This assessment is based on a single patch release. Validate PHP/Laravel/Filament version constraints and test coverage in the repository before committing.

How to Pitch It (Stakeholders)

For executives: This is a small, low-risk UI dependency for our Filament admin tooling. It replaces custom modal-and-table selection code we would otherwise build and maintain ourselves. The latest release (v1.1.4) is a bug-fix patch, not a feature or breaking change, so there is no migration cost or user-facing behavior change. The notable signal is maintenance health: an external user reported a defect and the maintainer shipped a focused fix quickly, which is what we want to see in a dependency we adopt.

For engineering: v1.1.4 fixes a type error in TableSelectLivewireComponent::mount() where a record action on an array-backed table passed a plain array into a property typed ?Model, throwing on trigger click. The mount now forwards the record only when it is an Eloquent model, which is correct since standalone mode never consumed it and relationship scoping only applies to Eloquent-backed tables. No API changes, no deprecations, no config changes — upgrade is a composer bump plus a regression check on any array-backed table that opens this picker. If you do not use array-backed tables, the fix is a no-op for you. Before adopting broadly, confirm the package's Filament version support and add a test covering the array-backed record-action path, since that combination is where the reported defect lived.