Advance Table Repeater Laravel Package

Product Decisions This Supports

• Build vs. buy for dense admin forms: This package replaces what is typically a custom-built, high-maintenance Filament extension (table-style repeater with per-column headers). Adopting it converts a multi-day internal build into a composer dependency, which is a straightforward win if we are already on Filament v5.
• Feature feasibility for data-dense editing UIs: Line-item editors (invoices, orders, quotes), schedule/shift grids, price-break tables, and multi-row configuration screens become a standard component rather than a bespoke design problem. This can unblock roadmap items previously deferred as "too much UI work."
• Read-only table output in the same visual language: RepeatableEntry plus toEmbeddedTableHtml() means the same table can appear in the admin panel and in transactional email/PDF templates without duplicating markup — relevant for any "record detail + confirmation email" flows.
• Operator experience as a product requirement: Column manager with session-persisted visibility, drag-and-drop row ordering, resizable columns, and a sticky summarizer footer are the features that reduce support tickets on wide tables. This lets us commit to "editable tables don't degrade on 8+ columns" as an actual quality bar.
• Scope control on custom JS: Summarizers (Sum, Count, Average, Range) and column behaviours (CanBeHidden, CanBeSummarized) are extension points, so aggregate/footer requirements can be met without a bespoke front-end task.
• Deployment/packaging decisions: Publishable config, views, and CSS plus an explicit panel plugin class means we can decide per-panel rollout, theme the CSS to our design system, and treat it as infrastructure rather than a fork.
• Roadmap risk flag: This is a v1.0.0 initial release. Plan for it as an early-adopter dependency: pin the version, isolate usage behind our own wrapper components where practical, and budget for upgrade churn as the API stabilises.

When to Consider This Package

Adopt when:

• The application is already on Filament v5 — the package targets v5 only and extends core Repeater / RepeatableEntry classes, so it is not portable to v3/v4 without a maintained release.
• Repeater-based forms are a recurring pattern and users are drowning in the default stacked layout — i.e., rows have 4+ comparable fields that benefit from column alignment.
• Editing density and scanability are a real usability complaint, not a hypothetical one; the column manager and sticky summaries only pay off on wide datasets.
• We want the read-only rendering of the same data in infolists and outbound mail without duplicating Blade templates.
• We are comfortable taking a young, single-purpose dependency whose whole value is UI-layer infrastructure with zero model coupling — the blast radius is contained to Filament form/infolist components.

Look elsewhere (or build) when:

• We are on Filament v3/v4, or have panels split across versions — no compatible path.
• Needs go beyond what's shipped: no mention of nested/grouped columns, per-row computed or editable-summary cells, server-side aggregation, or export. If the requirement is "spreadsheet," this is a table renderer, not a grid engine.
• Column visibility must persist per user across devices — session persistence is per-session, so a "my saved view" requirement is out of scope and would need custom work.
• We need a vendor with a support contract, SLA, or long release history; v1.0.0 with no prior assessment trail is early-adopter territory.
• The UI is not Filament (public-facing or Livewire-only surfaces) — the value is entirely in the Filament component lifecycle.

Recommended adoption gate: run a spike on one internal, low-traffic admin screen. Validate column manager behaviour, summarizer accuracy on empty/partial rows, drag-ordering persistence to the model, and a real mail embed via toEmbeddedTableHtml(). Promote to other panels only after that passes and we've confirmed the upgrade story.

How to Pitch It (Stakeholders)

For executives: We can ship a class of admin features — editable line-item and grid tables — that we have repeatedly scoped and deferred, by adding one small, free, open-source plugin instead of building and maintaining a custom component. It reduces estimated build effort for those screens and the ongoing maintenance burden that comes with custom front-end code. The trade-off is that it's a brand-new v1.0.0 dependency tied to Filament v5, so we're proposing a contained pilot on one screen rather than a broad rollout. Low cost, bounded risk, measurable time savings.

For engineering: Advance Table Repeater extends Filament\Forms\Components\Repeater and Filament\Infolists\Components\RepeatableEntry rather than replacing them, so it participates in normal Filament form/infolist state and validation — markAsRequired() is exposed per column. Columns are defined fluently via TableColumn with width, wrapping, resizability, and header controls; drag-and-drop ordering and column resizing ship out of the box. Summarizers are an abstract Summarizer with Sum, Count, Average, and Range implementations plus label(), so adding a custom aggregate is a small class, not a front-end change. Registration is a panel plugin (AdvanceTableRepeaterPlugin) plus a service provider with auto-discovery, publishable config (config/advance-table-repeater.php), views, and CSS — so it slots into our theme pipeline. There is zero model coupling, and it has full Pest coverage. Constraints to note: Filament v5 only, column visibility persists in session (not per user), and the summarizer set is client-side and fixed to four types. We should pin the version and wrap usage in our own components so the pending v1.x API churn is a one-file change.