- How do I install jeffersongoncalves/filament-hidden-action in a Laravel app?
- Install it with Composer using composer require jeffersongoncalves/filament-hidden-action. Your application must already be on filament/filament ^4.8, because the current release requires Filament 4.8 and explicitly requires filament/actions ^4.8. No new services, config publishing, or migrations are needed; registration fits into your existing Filament panel provider.
- What is HiddenAction used for in Filament?
- HiddenAction lets you define a Filament action that is not rendered in the UI but can still be triggered from code or via a keyboard shortcut. It is useful for admin panels that need the action's logic available without cluttering tables or pages with buttons users do not need. You keep the action registered in the normal Filament way while controlling whether it appears in the interface.
- Which Filament and Laravel versions does filament-hidden-action support?
- Version 1.0.3 requires filament/filament ^4.8 and adds an explicit filament/actions ^4.8 constraint. Filament 3.x is out of scope, and Filament 4.0 through 4.7 are not supported by this release. Treat the package as part of your Filament 4.8+ version line rather than an independent library, and check that your PHP version meets Filament 4.8's own floor.
- Why did filament-hidden-action 1.0.3 break my Composer install?
- 1.0.3 is labelled as a patch release but contains a breaking change: it raises the floor to filament/filament ^4.8 and adds filament/actions ^4.8. On applications pinned to Filament 4.0 through 4.7, Composer cannot satisfy those constraints and the install or update aborts. That hard failure is preferable to a silent mismatch, but it means automated dependency updates can turn red without an obvious minor or major version signal.
- How should I upgrade to 1.0.3 if I am still on Filament 4.7 or earlier?
- Upgrade Filament to 4.8 first in its own pull request with its own regression pass, then bump this package in a follow-up pull request. Combining both changes into one changeset makes it easy to hit a boot-time TypeError during route registration with an opaque stack trace. If you are already on Filament 4.8 or later, a normal composer update for this package is a low-risk patch bump.
- Can a HiddenAction be triggered by a keyboard shortcut?
- Yes. The package is designed so the action is absent from the visible UI but remains triggerable programmatically or through keyboard shortcuts. You define the action as usual and rely on the hidden presentation rather than a rendered button. This keeps admin screens clean while preserving the action's behaviour for power users and automation.
- How do I test a HiddenAction in my Laravel or Filament application?
- The package does not add separate testing infrastructure, so use your existing Laravel and Filament test setup. Because the action is not clickable in the UI, invoke it programmatically in a feature test and assert the state change it produces. That approach verifies the behaviour that matters without depending on a rendered button.
- Is filament-hidden-action actively maintained and what is its support policy?
- The package does not publish an independent support window; its compatibility follows Filament's release cadence because it reaches into Filament internals such as Page::routes(). Expect it to need updates when Filament minors touch routing. Check the repository for a changelog, upgrade guide, and test matrix covering Filament 4.8 and the current 4.x head before standardising on it.
- Is it safe to use ^1.0 with Dependabot or Renovate for this package?
- Be careful. Because 1.0.3 is a patch release that carries a breaking Filament version requirement, automated updates can move you onto a version that will not resolve against Filament 4.0 through 4.7. Pin the package alongside your Filament version and let the lockfile and CI catch resolution failures before deployment. Treat the package's version as coupled to your Filament minor.
- What alternatives exist for hiding Filament actions without this package?
- Filament's built-in visibility methods such as hidden() and visible(), plus policy and authorization checks, can keep actions out of the rendered UI in many cases. The difference here is a dedicated HiddenAction that is explicitly intended to stay hidden while remaining callable in code or via keyboard shortcuts. If you only need conditional button visibility, native Filament visibility may be enough.