[LIVECOPY-305] Can't protect inner fields of a multifield if PropertyNameDecorator is configured Created: 08/Mar/22  Updated: 18/Oct/22  Resolved: 18/Apr/22

Status: Closed
Project: Live Copy
Component/s: None
Affects Version/s: 3.2.7
Fix Version/s: 3.2.8

Type: Bug Priority: Neutral
Reporter: Roberto Gaona Assignee: Jesus Alonso
Resolution: Fixed Votes: 0
Labels: VN-Testing
Remaining Estimate: Not Specified
Time Spent: 2h 8m
Original Estimate: Not Specified

Attachments: PNG File image-2022-03-08-13-16-12-657.png    
Issue Links:
Problem/Incident
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Epic Link: AuthorX Support
Sprint: AuthorX 7
Story Points: 1

 Description   

Steps to reproduce

Configure a form field like the following:

properties:
  - name: typeExternal
    $type: compositeField
    propertyNameDecorator: info.magnolia.ui.field.PrefixNameDecorator
    i18n: false
    itemProvider:
      $type: currentItemProvider
      createIfMissing: true
    properties:
    - name: LinkText
      i18n: true
      $type: textField
    - name: Link
      i18n: true
      $type: textField
    - name: LinkTarget
      label: Target
      i18n: true
      $type: textField

Afterwards, trying to protect one of the inner fields won't apply the defined PropertyNameDecorator nor combine the composite field name with the inner field's name.

Expected results

Property name is properly generated and protects the field in question.

Actual results

Name generated ignores the configured PropertyNameDecorator, resulting on an incorrect property to be ignored.

Workaround

Removing the PropertyNameDecorator makes the issue inexistent, so in case of it not being necessary for the use case, removing it works as a workaround.

Development notes


Generated at Mon Feb 12 02:27:28 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.