Weave Code
Formtranslationchoice Bundle Laravel Package
liip/formtranslationchoice-bundle
LiipFormTranslationChoiceBundle adds a Symfony form choice type that translates option labels through the Symfony Translator, letting select, radio, and checkbox choices display localized text without manual label mapping.
[DEPRECATED] A Symfony2 bundle that provides a form widget and a validator that work with translation domains
Frequently asked questions about Formtranslationchoice Bundle
- Can I use liip/formtranslationchoice-bundle in Laravel?
- No. LiipFormTranslationChoiceBundle is a deprecated Symfony 2 bundle that ships a Bundle subclass and DI extension wired through AppKernel, and Laravel has no bundle concept, no kernel-registered container extension, and does not use the Symfony Form component. Installing it would require pulling symfony/form and symfony/validator into a Laravel app and building a bridge from Laravel's request lifecycle into Symfony's Form event model, which is net-new infrastructure for a feature Laravel already expresses natively.
- What does LiipFormTranslationChoiceBundle actually do?
- It provides a Symfony form choice type and a validator that translate option labels through the Symfony Translator so select, radio, and checkbox choices can display localized text without manual label mapping. The core idea is that labels and validation resolve against the same translation domain. That behavior is useful, but it is expressed entirely in Symfony Form APIs that Laravel never invokes.
- Is liip/formtranslationchoice-bundle still maintained?
- No. The repository is marked DEPRECATED and archived, has roughly 10 stars and zero dependents, and shows no CI, test matrix, or active maintainer. It targets Symfony 2, which reached end of life in 2016–2017. Archived status means no fixes or security patches will ever land.
- How do I translate select option labels in Laravel without this package?
- Define your choices once as a backed enum or config array and resolve each label with __('forms.status.'.$value) in a Blade partial or a dedicated x-select component. Because the same source of truth feeds both rendering and validation, labels and accepted values cannot drift. This typically takes 50 to 150 lines and needs no extra Composer dependency.
- Does this bundle support Laravel 10, 11, or 12?
- No. The package has no Laravel support at any version because it is built on Symfony 2-era Form and Validator APIs, including signatures like OptionsResolverInterface, setDefaultOptions(), and AbstractType::getName() that were removed in Symfony 3 and 4. Modern PHP 8 compatibility is unlikely without a fork. Laravel applications should not depend on it.
- Will installing this bundle cause Composer conflicts in a Laravel app?
- Very likely. Symfony 2 component requirements would conflict with the symfony/* packages Laravel already constrains, such as HttpFoundation, Console, Process, and VarDumper. That creates resolution deadlocks or forces pinned, unpatched component versions. The license is MIT, so the risk is lifecycle and dependency resolution, not legal.
- What is the Laravel equivalent of the Symfony translation choice form type?
- There is no package equivalent, and none is needed. In Laravel the pattern is a FormRequest with Rule::in(array_keys($choices)), an attributes() method returning translated field labels, and a Blade component that loops the same choices array. Use __('forms.status.'.$value) for the displayed label and validate against the matching raw value. Feature tests can assert both localized labels and rejection of out-of-domain values per locale.
- How do I validate a submitted choice against a translation domain in Laravel?
- Keep the canonical list of accepted values in a backed enum or config file and validate with Rule::in(MyEnum::values()) or Rule::enum(MyEnum::class). Return the allowed keys from the same source used to render labels, so translation keys and valid values stay aligned. A FormRequest handles this cleanly and keeps the controller thin.
- Is LiipFormTranslationChoiceBundle a security risk?
- The package itself has no known vulnerability in the usual sense, but it has no security response path. It is archived with no maintainer, no CI, and no stated test matrix, so any future issue would go unfixed. If your project has audit or regulatory requirements for supported dependencies, it fails immediately.
- What are the best alternatives to LiipFormTranslationChoiceBundle for Laravel?
- For Laravel, the alternative is native code rather than another package: a backed enum or config array, __('domain.key') labels, Rule::in or Rule::enum validation, and a Blade or x-select component sharing one source of truth. If you must reuse the exact constraint semantics, port the logic into app/Support behind an interface rather than vendoring the bundle. Treat the repository as a design reference only.
Weaver
How can I help you explore Laravel packages today?