- What is filament-keyable used for?
- It is a Filament plugin for managing API keys for any model in a Laravel application. Built on givebutter/laravel-keyable, it lets you associate incoming API requests with their models and control authorization through Policies. It is aimed at admin panels that need key, slug, or reference-code management inside Filament.
- How do I install jeffersongoncalves/filament-keyable?
- Install it with Composer using composer require jeffersongoncalves/filament-keyable, then register the plugin in your Filament panel provider if the package documentation requires it. Publish config, assets, or migrations only when instructed by the package. Clear Laravel caches after installation and verify the plugin appears in your panel.
- Which Laravel and Filament versions are supported?
- The package is a Filament plugin, so its supported Filament major version must match your panel. The provided assessment did not include composer.json constraints, so check the repository or Packagist metadata before adoption. Confirm Laravel, PHP, and Livewire compatibility for your target application.
- Does filament-keyable work with any Eloquent model?
- The package is described as providing keyable support for any model and is built on givebutter/laravel-keyable. You add keyable behavior to the model that should own API keys. Authorization is then handled through Policies, so model-level access rules remain in your application.
- How does API key authorization work in filament-keyable?
- The package overview says key authorization is managed through Policies. That means you define policy methods for the keyable model and let Laravel's authorization layer decide who can create, view, or manage keys. Review and test your policies before exposing key management in production.
- Is filament-keyable tested and production-ready?
- It can be used in production Laravel and Filament applications, but the assessment flags a single primary maintainer and does not confirm test coverage details. Treat it as a dependency to evaluate in staging first. Pin the version and verify key-management flows, locale behavior, and Filament compatibility before rollout.
- What changed in filament-keyable 1.2.0?
- Version 1.2.0 is mainly an internationalization expansion, adding 16 locales including ar, de, fr, ja, ru, tr, uk, and zh_CN. It also includes CI and dependency-maintenance changes. No breaking changes, migrations, or deprecations are indicated in the release notes.
- Does filament-keyable support translations and RTL locales?
- The 1.2.0 release adds locales such as Arabic and Persian, which are RTL, plus many LTR locales. RTL layout and directionality still depend on Filament and your application's CSS handling, not only translation files. Verify translations and locale-code mapping, especially zh_CN, in staging.
- How do I upgrade filament-keyable from 1.1.1 to 1.2.0?
- Treat 1.2.0 as a routine minor upgrade: update the Composer constraint, run composer update, and clear config and view caches. No data migration is indicated by the release notes. Test locale switching and key-management screens in staging before production.
- What are alternatives to filament-keyable?
- Alternatives include using givebutter/laravel-keyable directly with custom Filament resources, or building key management with Laravel Sanctum or Passport where API tokens fit the use case. If you need drop-in Filament UI for keyable models, this package may reduce custom code. Compare maintenance, Filament version support, and authorization needs before choosing.