[MGNLUI-2476] JCR browser: natural order of properties Created: 03/Jul/13 Updated: 10/Mar/21 Resolved: 10/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | configuration, content app |
| Affects Version/s: | 5.0, 6.2 |
| Fix Version/s: | 6.2.6 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Tom Wespi | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | AdminCentral, Tree, ux | ||
| 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: |
| Description |
|
At the moment, properties are re-ordered after renaming. So if you have a lot of properties and change "aaa" to "zzz" the field is not visible anymore (out of the window view). Even if is still selected. In my opinion there is no ordering of properties necessary anyway. Leave them there where created. |
| Comments |
| Comment by Andreas Weder [ 04/Dec/13 ] |
|
Renamed "nodedata" to "property" in the description and title. I'm assigning this to 5.x maintenance to have it discussed. At first glance, I see this option to fix this:
While 2) sounds like a nice thing to have, we have to keep in mind that, especially with large lists of properties, not sorting them also makes it hard to find a specific property. Of course, you could use search for that. |
| Comment by Tobias Mattsson [ 04/Dec/13 ] |
|
Moved ticket to MGNLUI project. |
| Comment by Jan Haderka [ 10/Mar/21 ] |
|
Properties are being sorted in order to make it easier to find them in longer lists. |