- What is jeffersongoncalves/filament-widget-configuration used for?
- It lets you define global defaults for Filament dashboard widgets, such as polling intervals and lazy loading, from a config file or your AppServiceProvider instead of editing each widget class. The package also provides a UI for choosing which widgets appear, reordering them, and adjusting widget settings so users can personalize their dashboard without code changes. It is intended for Laravel applications that use Filament panels.
- How do I install filament-widget-configuration with Composer?
- Run composer require jeffersongoncalves/filament-widget-configuration in your Laravel project. Then follow the package setup steps for your Filament panel, which typically includes registering the plugin in your panel provider. Check the README for any required publish or migration commands before using the UI.
- How do I publish the configuration file?
- Use the standard Laravel vendor publish command for the package, for example php artisan vendor:publish --tag=filament-widget-configuration-config. Confirm the exact tag in the package README. Publishing lets you edit defaults like polling interval and lazy loading in one place.
- Which Laravel and Filament versions are supported?
- The package is built for Laravel applications that use Filament panels. Supported Laravel and Filament versions are declared in the package composer.json, so check those constraints before installing. If you are on an older Filament major version, confirm compatibility or pin a matching package release.
- Can I set widget defaults in AppServiceProvider instead of a config file?
- Yes. The package supports configuring global widget defaults either through the published config file or programmatically in your AppServiceProvider. Use the config file for simple static defaults and the service provider when you need environment-specific or conditional logic. Keep the two approaches consistent to avoid confusion.
- Does it let each user customize their own dashboard widgets?
- Yes, the package includes a UI where users can choose which widgets appear, reorder them, and adjust widget settings. This lets each person personalize their dashboard without code changes. Global defaults still apply as the baseline unless overridden.
- How do I test widget configuration in my Laravel app?
- Write feature tests that boot a Filament panel with the plugin registered and assert the expected widget defaults or user preferences. Use Laravel testing helpers and, if the package provides them, its own test utilities. Clear cached config between tests so changes to defaults are picked up.
- Will changing widget defaults affect existing users?
- Global defaults set in config or AppServiceProvider generally act as the baseline for widgets that do not have user-specific preferences. Existing per-user customizations should remain intact, but test this in a staging environment. Clear any configuration cache after changing defaults in production.
- What are alternatives to filament-widget-configuration?
- You can implement similar behavior manually by overriding widget properties in each class or a base widget, and by building your own dashboard preference UI. Other Filament dashboard customization plugins may offer overlapping features, so compare maintenance status and Filament version support. This package is a focused option if you want global defaults plus a simple per-user widget picker.
- Is filament-widget-configuration actively maintained?
- Maintenance activity should be checked on the package repository and Packagist release history before adopting it. Look at recent commits, open issues, and whether the declared Laravel and Filament constraints match your project. If the repository is not actively updated, pin a known-good version and plan for a fallback.