- What is codewithdennis/filament-translate-field used for?
- It is a single-purpose Filament form field for managing translations across multiple locales. Editors get locale tabs and a one-click translate action that writes translated values into array or JSON-backed columns on the model. It is intended for multilingual admin panels where editors enter and switch between language versions of content.
- How do I install and register the translate field in Filament?
- Install it with Composer, then register the field in a Filament form schema and configure your locale list. You will also need to configure a translation provider before the one-click action can work. Check the package source and composer.json for the exact service provider and field registration details.
- Which Laravel and Filament versions does this package support?
- The available context does not list exact PHP, Laravel, or Filament version constraints. Read composer.json before estimating work, and confirm support for both your current Filament major and the version on your roadmap. The last release was 2024-10-10, so verify compatibility carefully against newer Filament releases.
- Which translation provider does it use, and can I swap or self-host it?
- The context confirms a translation provider must be configured but does not identify the API, key mechanism, or whether egress to a third party is mandatory. Inspect the action source to see whether the provider sits behind an interface or is hardcoded. For production use, put the provider behind an internal service interface so it can be swapped or self-hosted later.
- Does the package send my form text to a third party?
- The one-click translate action implies that user-authored text is sent to the configured translation provider, which may be a third party. That is a procurement, DPA, and data-residency question rather than a code question. Get a written answer before using it on PII, customer data, or regulated content.
- How does the field store translations in the database?
- It writes translated values into array or JSON-backed translation columns on the model. The field renders locale tabs and lets editors switch between language versions in the form UI. It is not a full translation management system: there is no translation memory, glossary, reviewer role, per-locale publish state, or audit trail.
- Does it preserve HTML, markdown, and line breaks?
- The context does not guarantee that machine output preserves HTML, markdown, or line breaks. Test with your actual content types and validation rules, including max lengths and per-field validation. Add a visible machine-translated review marker and avoid saving machine output as authoritative without review.
- Is the package actively maintained, and is it safe for production?
- It is archived, has about 10 stars, zero dependents, and its last release was 2024-10-10. That means no community validation, no upstream response to a Filament major bump, and no security patch path. A field-level convenience likely does not justify an unmaintained production dependency; vendor the pattern instead.
- Can I vendor or fork the package, and what license applies?
- It is MIT licensed, so you can inspect, fork, and vendor it with attribution. Because the repository is archived, vendoring is the safer path if you want the interaction pattern without upstream lock-in. Put the translate call behind one internal service interface so a later provider swap is a config change, not a refactor.
- How should I test the translate action and handle provider outages?
- Mock the provider and assert that translations land in the JSON column, that manual edits are not overwritten by a racing async action, and that validation rules still apply. Test expired keys, quota exhaustion, and provider outages to confirm graceful fallback to manual entry rather than a hard failure. Review whether the package has meaningful test coverage before carrying it as a dependency.