[MGNLUI-392] Allow tree view to keep the JCR order of nodes Created: 11/Dec/12  Updated: 11/Feb/13  Resolved: 24/Dec/12

Status: Closed
Project: Magnolia UI
Component/s: configuration, content app
Affects Version/s: 5.0
Fix Version/s: 5.0

Type: Improvement Priority: Major
Reporter: Jozef Chocholacek Assignee: Federico Grilli
Resolution: Duplicate Votes: 0
Labels: framework
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLUI-450 Do not sort items in trees alphabetic... Closed
duplicate
duplicates MGNLUI-450 Do not sort items in trees alphabetic... 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)
Date of First Response:

 Description   

In the Config App, the nodes are sorted alphabetically - but e.g. for filters, the native JCR order is needed to be clear in which order are they applied. And there are more places where the order (the JCR one) of nodes is important.

So the TreeView in workbench must allow to be turned to "keep JCR order" mode.



 Comments   
Comment by Federico Grilli [ 14/Dec/12 ]

I would say that the tree view (or more precisely info.magnolia.ui.admincentral.tree.container.HierarchicalJcrContainer) should not do any sorting at all and just reflect the order as it is in the JCR repository. I think that doing a lexicographical pre-ordering of nodes by default, as we do now, is most confusing for users. I think there are plans to support sorting of trees in the UI but that is an operation explicitly triggered by a user in the UI and is reversible in the sense that one can always close an app and get again JCR repo order.

Comment by Andreas Weder [ 21/Dec/12 ]

I'm connecting these two issues because they cover the same topic. MGNLUI-450 offers some ideas on how sorting in the tree view could work, though.

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