- What is akunbeben/inline-confirm and what does it do?
- It is a lightweight Laravel package that replaces native browser confirm dialogs with inline confirmation prompts for destructive actions such as delete buttons, so users stay in context instead of facing a modal. The current 1.x line is published as akunbeben/fluid-actions and ships as a Filament UI plugin with inline confirmation and hold-to-confirm interaction patterns. It is a presentation-layer concern only and does not touch persistence, queues, auth or domain logic.
- How do I install it in a Laravel application?
- For a new install, run composer require akunbeben/fluid-actions:^1.0 and register FluidActionsPlugin on the relevant Filament panel. Optionally publish the package assets and views with php artisan vendor:publish using the fluid-actions tag. Only use the legacy akunbeben/inline-confirm name if you already have a pre-1.0 installation to migrate.
- Which Filament, Laravel and PHP versions are supported?
- The package is a Filament UI plugin and the technical assessment scopes it to Filament v3 or v4 panels on PHP 8.2 or newer. The compatibility matrix is flagged as an open question, so confirm the documented Filament major, Laravel and PHP constraints against your own panels before rollout. Do not assume it applies to non-Filament admin surfaces.
- Can I use it without Filament, for example in plain Blade or Livewire?
- The 1.x fluid-actions release is a Filament UI plugin, and the assessment explicitly says it is not applicable to non-Filament surfaces such as Nova, plain Bootstrap or a Blade and Livewire admin. The pre-1.0 inline-confirm blurb mentioned simple Blade integration, but that is not the scope of the current package. Scope the rollout to Filament panels and do not try to generalise it.
- How do I publish and customise the package views and assets?
- Run php artisan vendor:publish with the fluid-actions tag to publish the CSS, JS and Blade views, adding --force on deploys that must overwrite stale files. Published assets typically live in public/ and are often gitignored, so make sure the deploy pipeline re-publishes them. Reference the fluid-actions view namespace in any custom Blade you write.
- How do I change the confirmation labels and styling?
- Publish the views and assets, then edit the published Blade views to change button labels and confirmation copy and the published CSS to adjust styling. Customisation stays in views and stylesheets because the package is a presentation-layer plugin with no domain config. Keep custom views aligned with the fluid-actions namespace after the rename.
- Why did my custom action view disappear when I enabled inline confirmation?
- That was a configuration-fidelity bug fixed in v1.0.0, where enabling inline confirmation or hold-to-confirm could overwrite the original explicit action view. Upgrade to 1.0.0 so the package preserves your custom view. Also check that any custom view references use the new fluid-actions namespace after the rename.
- How do I migrate from akunbeben/inline-confirm to akunbeben/fluid-actions?
- Treat it as a hard substitution in one dedicated PR: remove the old package, require akunbeben/fluid-actions:^1.0, update imports from Akunbeben\InlineConfirm to Akunbeben\FluidActions, and switch plugin registration and view namespace references to FluidActionsPlugin and fluid-actions. Run php artisan vendor:publish --tag=fluid-actions --force and delete orphaned public/css/inline-confirm.* and public/js/inline-confirm.* files. Search the codebase for the literal string inline-confirm as an acceptance check.
- Why is the confirmation UI unstyled or broken after upgrading?
- The rename changed the published CSS and JS filenames, so environments still serving the old inline-confirm assets will get a silent 404 rather than a clean error. Re-run php artisan vendor:publish --tag=fluid-actions --force in the deploy pipeline and remove the stale asset files. Check any hard-coded asset tags in Blade for the new fluid-actions filenames.
- What changed in v1.0.0 and is it safe to use in production?
- v1.0.0 is a full rename from akunbeben/inline-confirm to akunbeben/fluid-actions plus two fixes: preserving the original explicit action view when inline confirmation or hold-to-confirm is enabled, and correctly storing the closeDropdown configuration. Functionally it is a low-risk leaf presentation dependency, but the dominant release risk is nominal because every renamed identifier is public. Audit for legacy inline-confirm references in code, lockfiles and feature branches, and confirm your deploy step re-publishes assets with --force.