IBX-8508: Fixed translation_domain working incorrectly for dropdowns#1286
Open
IBX-8508: Fixed translation_domain working incorrectly for dropdowns#1286
translation_domain working incorrectly for dropdowns#1286Conversation
Contributor
|
@Steveb-p is there any Jira issue related to this PR? |
Contributor
Author
|
After internal sync we decided to push this change onto 5.0 series to prevent breaks. |
31a2674 to
a46d436
Compare
|
translation_domain working incorrectly for dropdownstranslation_domain working incorrectly for dropdowns
konradoboza
approved these changes
Jul 9, 2024
src/bundle/Resources/views/themes/admin/ui/form_fields/dropdown_widget.html.twig
Show resolved
Hide resolved
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



For QA:
We will need to check label translations in other parts of admin UI. Some parts might no longer be translated, since they would be using old
translation_domainoption (instead ofchoice_translation_domain, as they should).Description:
Relevant excerpt from discussion that was happening in a different, closed source PR:
With this approach and properly set
translation_domainandchoice_translation_domain:Documentation: