a2lix/translation-form-bundle
Full Changelog: https://github.com/a2lix/TranslationFormBundle/compare/4.0.3...4.0.4
Full Changelog: https://github.com/a2lix/TranslationFormBundle/compare/4.0.2...4.0.3
Full Changelog: https://github.com/a2lix/TranslationFormBundle/compare/4.0.1...4.0.2
Full Changelog: https://github.com/a2lix/TranslationFormBundle/compare/4.0.0...4.0.1
Complete rewrite. See https://github.com/a2lix/TranslationFormBundle/blob/main/README.md BC. See https://github.com/a2lix/TranslationFormBundle/blob/main/UPGRADE-4.0.md
Full Changelog: https://github.com/a2lix/TranslationFormBundle/compare/3.2.4...4.0.0
Full Changelog: https://github.com/a2lix/TranslationFormBundle/compare/3.2.3...3.2.4
Full Changelog: https://github.com/a2lix/TranslationFormBundle/compare/3.2.1...3.2.3
Full Changelog: https://github.com/a2lix/TranslationFormBundle/compare/3.2.0...3.2.1
This minor release allows AutoFormBundle ^0.4 following https://github.com/a2lix/AutoFormBundle/pull/29
Full Changelog: https://github.com/a2lix/TranslationFormBundle/compare/3.1.0...3.2.0
This release allows Symfony 6.0+ and adds new tests for PHP8.0 and PHP8.1 in the CI workflows
Full Changelog: https://github.com/a2lix/TranslationFormBundle/compare/3.0.10...3.1.0
This release only adds a small feature to allow customisable labels for translation
Add translatable locale labels (#365)
You may now set labels for each tab by adding a locale_labels array to the TranslationsType form type, like so:
$form = $this->factory->createBuilder(FormType::class, new Product())
->add('translations', TranslationsType::class, [
'locale_labels' => [
'fr' => 'Français',
'en' => 'English',
],
])
->add('save', SubmitType::class)
->getForm()
;
If a label is not set here (in this examplen de for instance), its value will default to null and the previous behaviour will kick-in (the template with capitalize the locale name).
Hence, this does not introduce any breaking change and no change of defaults, and seems perfectly safe.
As the trans filter is used in the templates, you can also use translation keys directly here:
$form = $this->factory->createBuilder(FormType::class, new Product())
->add('translations', TranslationsType::class, [
'locale_labels' => [
'fr' => 'admin.language.fr.tab_title',
'en' => 'admin.language.en.tab_title',
],
])
->add('save', SubmitType::class)
->getForm()
;
See also: https://a2lix.fr/bundles/translation-form/3.x.html#bundle-usage
Fix multiple partial translations (#354) — Thanks @adelinerobinet
This release might introduce a BC break if you were using the id attribute of a partial translation div to target it in CSS or Javascript, like so for instance:
#Article_translations_fr_a2lix_translations-fields {
border: 1px solid green;
}
You must now use the full id that includes a concatenation of field names (See here)
symfony/config ^4.2setRequest on the xml configuration fixes scope wideningTranslatedEntityType::setRequest is deprecated, consider using setRequestStack insteadTranslatedEntityType is now compatible with choice_label for Symfony >= 2.7Fix #219
https://github.com/a2lix/TranslationFormBundle/pull/165 https://github.com/a2lix/TranslationFormBundle/pull/166 https://github.com/a2lix/TranslationFormBundle/pull/169 https://github.com/a2lix/TranslationFormBundle/pull/182 https://github.com/a2lix/TranslationFormBundle/pull/188 https://github.com/a2lix/TranslationFormBundle/pull/190 :warning: about not BC with CSS class change if you use the default template. https://github.com/a2lix/TranslationFormBundle/pull/214
How can I help you explore Laravel packages today?