[MGNLUI-5812] JcrMultiField subnodes are wrongly indexed Created: 09/Apr/20  Updated: 09/Oct/20  Resolved: 11/May/20

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2
Fix Version/s: 6.2.1

Type: Bug Priority: Neutral
Reporter: Adam Siska Assignee: Adam Siska
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 0.75h
Original Estimate: Not Specified

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
Epic Link: MultiFields compatibility
Sprint: UI FW 1, UI FW 2
Story Points: 2

 Description   

Steps to reproduce

  1. Take jcrMultiField definition from https://documentation.magnolia-cms.com/display/DOCS62/Multi+field#Multifield-JCRmultifieldexample and add it to, e.g. contacts-v8 app in editContact.yaml.
  2. create more then ten entries and save.

Expected results

In JCR you should see multi9 followed by multi10

Actual results

After multi9 subnode it goes to multi110, multi111, ...

Development notes  

This is caused by regex matching: info.magnolia.ui.editor.DefaultJcrNodeOrderHandler#INDEX_PATTERN


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