Filament Copyactions Laravel Package

Getting Started

The v4.0.2 release is a compatibility release: the main change is support for Filament 5.0. Treat it as a low-feature-risk but compatibility-sensitive update. If your app is still on Filament 4, do not assume this package version is a drop-in replacement; verify composer.json constraints first.

• Start with composer.json: confirm the package requires filament/filament:^5.0 and that your app’s Filament constraint matches.
• Read the package README and CHANGELOG/UPGRADE notes for Filament plugin registration, publish tags, and any v4 migration notes.
• Inspect the package service provider and Filament plugin class to see what is auto-registered versus what must be registered in a panel provider.
• Publish only what you need: config, migrations, translations, views, or assets. Use tagged publishes where available.
• First use case: install ^4.0, register the package’s Filament plugin in a panel provider, then expose one resource/page/widget that uses the package’s main feature.

Minimal install shape:

composer require vendor/package:^4.0
php artisan vendor:publish --tag=package-config
php artisan migrate
php artisan optimize:clear

Then register the plugin in the relevant Filament panel provider:

->plugin(PackagePlugin::make())

Implementation Patterns

• Panel-scoped registration: Register the package plugin on each Filament panel that needs it. Avoid global boot logic if the package supports multi-panel apps.
• Config-driven behavior: Keep package options in config/package.php and environment variables. This is important for per-environment asset, route, and feature toggles.
• Resource/page integration: Use the package inside Filament resources, pages, widgets, actions, or form/table schemas according to its documented extension points. Prefer public APIs/traits over subclassing vendor internals.
• Authorization first: Wire policies, gates, and tenancy scoping before adding UI. Filament panels make it easy to expose actions accidentally if authorization is deferred.
• Upgrade workflow: Create a branch, update Composer constraints, run composer update vendor/package --with-dependencies, publish new assets/config if required, run migrations, clear caches, then smoke-test the panel.
• Testing workflow: Use Filament’s testing helpers where available. Set the current panel explicitly in tests, assert plugin registration, resource visibility, authorization, and one end-to-end package workflow.
• Multi-panel apps: Instantiate plugin configuration per panel rather than relying on static state. Check that routes, navigation groups, and assets do not collide.
• Deployment: After deploy, run php artisan optimize:clear, re-publish Filament assets if the package ships them, and rebuild frontend assets if the package depends on them.

Gotchas and Tips

• Compatibility is not transitive: Package v4.0.2 supporting Filament 5 does not mean your app is ready. Use composer why-not filament/filament "^5.0" and composer show to diagnose conflicts.
• Patch release expectations: v4.0.2 likely adds Filament 5 compatibility rather than new package features. Do not plan new functionality around this patch.
• Filament 5 breaking changes: Filament major upgrades can affect plugin APIs, asset handling, panel registration, and testing helpers. Check both the package upgrade notes and Filament 5 upgrade guide.
• Config cache surprises: If behavior changes only in production, check cached config/routes. Clear caches after changing package config or panel registration.
• Publish tags: Do not blindly re-publish and overwrite customized config/views. Diff published files before deploying.
• Panel registration order: If the package depends on Filament navigation, auth, or tenancy, register it after the core panel configuration it relies on.
• Authorization gaps: Filament resources/pages can be reachable by direct URL. Test policies and tenant scoping, not just navigation visibility.
• Asset issues: If styles/scripts disappear after upgrade, re-publish package assets and run the app’s frontend build. Check php artisan filament:assets if supported by your Filament version.
• Debugging checklist: php artisan about, composer show vendor/package, composer why-not, php artisan route:list, php artisan optimize:clear, and storage/logs/laravel.log.
• Extension points: Prefer the package’s documented plugin config, events, bindings, and published config. Avoid editing vendor files or overriding internal classes that are likely to change across Filament majors.