- What does pxlrbt/filament-translate-action do?
- It adds a configurable Translate action to Filament resources so editors can translate translatable model fields between locales from a modal without leaving the admin panel. It integrates with Filament tables and forms for quick multilingual content workflows. It is an admin-panel UI extension rather than core domain or runtime infrastructure.
- How do I install pxlrbt/filament-translate-action in a Laravel app?
- Install it via Composer in a Laravel application that uses Filament, then register or use the action on translatable resources. Ensure your translation strategy, locales, and model fields are configured. The release notes do not indicate new services, queues, or infrastructure.
- Which Filament versions does pxlrbt/filament-translate-action support?
- Version 1.2.0 declares compatibility with Filament v5. The release note does not state whether older Filament majors are preserved or dropped. Treat older-version compatibility as unproven until you verify the package composer.json constraints and CI.
- Does pxlrbt/filament-translate-action work with Filament v3 or v4?
- The provided release context does not confirm support for Filament v3 or v4. Version 1.2.0 specifically calls out Filament v5 support, so do not upgrade blindly on older Filament majors. Check the package composer constraints and changelog, or pin a compatible package version.
- What Laravel and PHP versions are required by pxlrbt/filament-translate-action?
- The provided information does not list the exact Laravel and PHP version matrix. Validate the package composer.json against your application and Filament v5 constraints. Pin the package version and test against your exact Laravel, PHP, and Filament versions.
- Does pxlrbt/filament-translate-action require a specific translation backend or model trait?
- The package translates translatable model fields, so your underlying translation strategy, locales, and model fields must already be configured. The provided context does not specify a required translation backend or model trait. Review the source and Composer requirements before choosing a translation package.
- Can pxlrbt/filament-translate-action run queued or batch translations?
- The context describes it as an admin action for translating fields from a modal, with no indication of queued or batch translation support. The technical assessment notes that throughput and rate limits matter if the action calls external translation APIs or processes many fields and locales synchronously. Check the documentation and source for any queue or batch features.
- How do I control who can trigger translations with this Filament action?
- The package is a Filament action, so authorization is likely handled through Filament action and resource policies, but the release note does not detail authorization changes. Test permissions carefully alongside locale switching and validation. Restrict action visibility in Filament for users who should not translate content.
- What should I test before deploying pxlrbt/filament-translate-action v1.2.0?
- Test the action on a representative translatable resource, including locale switching, permissions, validation, and translation-provider behavior. Verify API credentials and rate limits if an external translation service is used. Check for partial translations that could leave content inconsistent, then roll out to staging before production.
- What are the risks of upgrading pxlrbt/filament-translate-action to v1.2.0 for Filament v5?
- The main risk is dependency alignment because Filament v5 is a major ecosystem change and the package changelog is sparse. Verify the Composer matrix and sequence the Filament v5 upgrade before adopting this package version. Pin the package and validate action registration, authorization, locale handling, and translation-provider behavior in a branch.