- Does saadj55/filament-copyable work with Filament v3 or Laravel 10 and 11?
- The package's last release was 2022-10-12, which strongly suggests it targets the Filament v2 era rather than Filament v3 or later. Filament v3 and newer Laravel versions are likely unsupported without a fork. Check the package composer.json constraints and test against your exact Filament version in staging before adopting it. For Filament v3+, building a small internal copyable column or action is usually safer.
- How do I install filament-copyable in a Laravel Filament application?
- Installation is a standard Composer require for saadj55/filament-copyable, followed by using the package's copyable column and field components in your Filament resources. The overview states minimal setup with no extra configuration required, but you should still verify Composer constraints against your Filament version first. Test one table column and one form field in a non-critical admin screen before rolling it out.
- Which Laravel, PHP, Filament, and Livewire versions does this package support?
- The provided context does not list exact version constraints, but the 2022 release date points to Filament v2-era compatibility and older Laravel and PHP versions. You must inspect the package composer.json for PHP, Laravel, Filament, Livewire, and Alpine requirements before installing. Do not assume compatibility with current Laravel or Filament releases without testing.
- Is filament-copyable maintained and safe to use in production?
- It is community-only with no vendor SLA, no recent release, and few community signals such as stars or dependents. The MIT license allows a fork, but maintaining a fork for such a small feature is often worse than implementing it internally. If adopted, pin the exact version, review the source, restrict copyable fields to low-risk identifiers, and add a smoke test.
- How does the copy-to-clipboard behavior work in Filament tables and fields?
- The package adds a client-side copy button to Filament columns and text fields, likely using the browser Clipboard API and Alpine.js. Clicking the control copies the cell value and can show customizable icons, tooltips, and success notifications. No backend service or domain logic is involved, so server impact is negligible.
- Can I customize the copy icon, tooltip, and success notification?
- The package overview advertises customizable icons, tooltips, and success notifications. The exact API is not documented in the provided excerpt, so check the package source or README for method names and configuration options. Default behavior is described as minimal setup with no extra configuration required.
- What happens if the browser blocks clipboard access or the site is not HTTPS?
- The Clipboard API generally requires a secure context and user permission, so copy actions can fail on plain HTTP or when permission is denied. The provided context does not confirm a fallback or failure notification. Validate permission-denied and insecure-context scenarios in staging, and consider adding explicit user feedback or an internal fallback if the package does not provide one.
- Is there a security risk in making Filament columns copyable?
- Any copyable cell can be placed on the clipboard, where it may persist and be readable by other applications. Restrict copy behavior to approved low-risk fields such as IDs, slugs, or reference numbers, and avoid enabling it for secrets or sensitive personal data unless explicitly authorized. Review the allowlist of copyable fields as part of your security review.
- How does filament-copyable compare with building a copy action using Alpine.js in Filament?
- The package is a thin presentation-layer utility that can be replicated with a small Alpine.js directive or a Filament action that copies a value. Given the abandonment and Filament v3 compatibility risk, an in-house implementation is often the lower-maintenance option for long-lived admin panels. Use the package as-is only if you are on a compatible Filament v2 stack and pin the version.
- Does filament-copyable include tests or documented browser support?
- The provided context does not mention automated tests or documented browser support. Treat browser behavior as unverified and test across your supported browsers, HTTPS, and clipboard permission-denied cases. If you adopt the package, add a smoke test and document ownership for future Filament upgrades.