[MGNLPN-196] Make use of new i18nized complex fields from UI Created: 20/Nov/14  Updated: 11/Mar/21  Resolved: 11/Mar/21

Status: Closed
Project: Magnolia Personalization
Component/s: Integration, Traits
Affects Version/s: None
Fix Version/s: 1.1.x, 1.2.x

Type: Bug Priority: Minor
Reporter: Philip Mundt Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-3169 I18n'ize complex fields 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

 Description   

The following fields use info.magnolia.ui.form.field.AbstractCustomMultiField which has added info.magnolia.ui.api.i18n.I18NAuthoringSupport:

  • info.magnolia.personalization.ui.TraitValueCompositeField
  • info.magnolia.personalization.ui.TraitAggregatorField

We should use the new constructors.

Similarly, the info.magnolia.personalization.date.system.DateTraitField now use deprecated constructor, info.magnolia.personalization.date.system.DateTraitFieldFactory needs to be adjusted too.



 Comments   
Comment by Philip Mundt [ 20/Nov/14 ]

info.magnolia.personalization.date.system.DateTraitField was done in:

Generated at Mon Feb 12 06:35:15 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.