Filament Tree Table Laravel Package

Product Decisions This Supports

• Feature scope for admin/data tables: lets end users choose which columns are visible, with expand-all/collapse-all and search affordances — a low-cost way to serve users with divergent information needs from a single table definition instead of shipping multiple views.
• Build vs. buy on table UX: the alternative is hand-rolling column visibility plus session persistence in every Filament resource. This is a narrow, well-bounded problem; buying in is defensible unless your requirements go beyond toggling (e.g., per-user saved views, column ordering, cross-device preferences).
• Roadmap sequencing against Filament upgrades: v1.3.1 raises the v4 floor from ^4.0 to ^4.3 (^4.3||^5.0) because the test suite depends on Table::persistColumnsInSession(), added in Filament 4.3. Adoption is therefore gated on being at Filament 4.3+ or 5 — worth folding into upgrade planning rather than discovering at install time. Composer resolves the newest 4.x on upgrade, so most teams are unaffected.
• Risk posture for the dependency: the release adds a rendering-level test suite (tables mounted through Livewire and actually drawn, not just query assertions), a CI matrix across PHP 8.2–8.5 × Laravel 11/12/13 × Filament 4/5, a lowest-supported-versions run, a SECURITY.md with a reporting address, and an automated tag-driven release. That combination is the signal that justifies adopting rather than vendoring a small internal helper.
• Support and triage load: session-scoped persistence means preferences do not follow users across devices or sessions with expiring storage. If stakeholders expect durable per-user layouts, that is a roadmap item, not something to promise off this package.

When to Consider This Package

Consider it when:

• You are on Filament 4.3+ or Filament 5 (hard requirement) and have data-heavy tables where different roles or users care about different columns.
• You want column visibility without owning the UI code or the session-persistence plumbing.
• Your team is small and would rather take a tested dependency than maintain a fork of table-rendering logic.
• You value upstream hygiene: security reporting policy, pinned CI actions with Dependabot upkeep, and releases that fail rather than publish empty notes.

Look elsewhere when:

• You are pinned to Filament 4.0–4.2 with no near-term upgrade path — this release will not install.
• You need persisted, per-user, cross-device table layouts; the session-scoped model is a mismatch.
• You need guarantees this package does not offer: formal support SLAs, long-term support branches, or vendor indemnity. This is a small, single-maintainer-scale dependency — plan for the option to fork.
• Your stack is not Filament, or you need table capabilities beyond visibility control (reordering, pinning, saved filter sets) — verify scope before committing.

How to Pitch It (Stakeholders)

To executives: A cheap, contained UX improvement for internal tools and admin panels. Users stop asking engineering to hide or show columns, and one table definition serves many audiences. Cost is a single small dependency; the main constraint is that it requires a recent Filament version, which we likely already run or get automatically on upgrade.

To engineering: A Filament column-manager plugin, now at v1.3.1. The v4 floor moves to 4.3 because the tests rely on persistColumnsInSession(); Filament 5 is unaffected. The release materially improves confidence: tables are now mounted through Livewire and rendered in tests (exercising the toggle column, chevrons, expand/collapse actions, and search), CI covers PHP 8.2–8.5 against Laravel 11–13 and Filament 4 and 5 plus a lowest-dependencies run, actions are SHA-pinned and updated by Dependabot, there is a SECURITY.md, and releases are published automatically from tagged sections of the changelog. Behaviour is unchanged — this is a tooling and constraint release, not a feature release.