[MGNLUI-6004] LinkFieldDefinitionConverter doesn't treat properly `targetTreeRootPath` property Created: 30/Jun/20  Updated: 22/Sep/21  Resolved: 13/Jul/20

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

Type: Bug Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Adam Siska
Resolution: Fixed Votes: 0
Labels: cs-bk
Remaining Estimate: Not Specified
Time Spent: 1h 7m
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLUI-6199 "targetTreeRootPath" Property Is Affe... 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:
Sprint: UI FW 5, UI FW 6
Story Points: 3

 Description   

From what it looks like the converted chooser gets its datasource definition resolved only via the specified app's content connector definition, but the old link field actually also allows specifying `workspace` and `rootPath` properties explicitly and those aren't considered by the converter.

AC:

  • mentioned two properties are handled (:?: and passed to the CompatibilityAppAwareWorkbenchChooserDefinition#resolveDatasourceFromAppName)
  • test case is written (can piggyback on the linked Blossom issue)


 Comments   
Comment by Christopher Zimmermann [ 07/Jul/20 ]

Regarding MGNLUI-5919, this would be great as it is also causing some support issues and makes it very challenging for a n M6 app to link to an M5 app. This will be often required in the year to come until all customers and extensions legacy apps can be ported.

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