[MGNLUI-2332] Detail subapps don't support custom root path Created: 29/Oct/13  Updated: 12/Nov/13  Resolved: 05/Nov/13

Status: Closed
Project: Magnolia UI
Component/s: content app
Affects Version/s: 5.1.1
Fix Version/s: 5.2

Type: Improvement Priority: Neutral
Reporter: Mikaël Geljić Assignee: Mikaël Geljić
Resolution: Won't Fix Votes: 0
Labels: detail-sub-app
Remaining Estimate: Not Specified
Time Spent: Not Specified
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)
Date of First Response:
Epic Link: Data module migration
Sprint: 5.2-rc1

 Description   

We should enable detail subapps to have a base path, like the workbench path for browser subapps.
It would have the following advantages:

  • selected item path looks consistent in the location fragment across subapps (including in detail subapp's tab title)
  • the base path is kept hidden in the location at all times


 Comments   
Comment by Tobias Mattsson [ 29/Oct/13 ]

Could we use a more descriptive name for getPath(), its not clear what this is the path to.

Comment by Mikaël Geljić [ 04/Nov/13 ]

Will revert because actions have no way to figure out what the rootPath is, and DetailSubApp or DetailEditorPresenter cannot know for sure that a path is relative of absolute.

Generated at Mon Feb 12 08:55:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.