[MGNLUI-3480] Sorting in content apps only works for JCR properties Created: 30/Jun/15 Updated: 13/Mar/20 Resolved: 13/Mar/20 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | content app, tree/list, workbench |
| Affects Version/s: | 5.3.9, 5.4.9 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Cedric Reichenbach | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | 1h | ||
| Time Spent: | 0.9h | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| 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 |
|
Sort data in a content app's list view only works correctly, if this column displays a JCR property. However, a column doesn't need to be directly bound to a JCR property and can basically display anything, like the "Status" column in some built-in apps. One elegant solution could be to let developers optionally configure a custom Comparator for a column definition. |
| Comments |
| Comment by Mercedes Iruela [ 27/Sep/16 ] |
|
This issue seems to be related to |