[MGNLUI-3818] SelectFieldFactory is not translating keys, if options are build from repository path Created: 18/Mar/16  Updated: 08/Mar/21  Resolved: 08/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: dialogs
Affects Version/s: 5.4.5
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Sergio Vidangos Assignee: Unassigned
Resolution: Inactive Votes: 0
Labels: dialogs, i18n, select
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLUI-3773 SelectFieldFactory should not transla... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

After the changes made in this revision, the labels of the options are not being internationalized anymore (only the keys are shown; the translations are not being loaded using the keys).

This happens in case the options are loaded from JCR using the parameters 'repository' and 'path' for a select field (info.magnolia.ui.form.field.definition.SelectFieldDefinition).

If the options are defined within the select field definition (yaml or JCR), the translation is working correctly.



 Comments   
Comment by Roman Kovařík [ 18/Mar/16 ]

Hello sergio.vidangos,

so you specify the translation keys in JCR nodes? Could you describe your use case?

Thanks in advance.
Roman

Generated at Mon Feb 12 09:10:23 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.