[MGNLUI-51] Ordering in content apps should rely on column names not on propertyNames Created: 22/Oct/12 Updated: 11/Feb/13 Resolved: 23/Oct/12 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 5.0 |
| Fix Version/s: | 5.0 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Daniel Lipp | Assignee: | Daniel Lipp |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| 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 |
|
Current implementation of AbstractJCRContainer & WorkbenchTreeTable use the propertyName (if defined) else the column name to decide what column will be used for ordering. Always using the column name would be much simpler. |
| Comments |
| Comment by Daniel Lipp [ 23/Oct/12 ] |
|
While it would work perfectly for the Container, this new pattern cannot consistently be applied to com.vaadin.ui.Table. |
| Comment by Tobias Mattsson [ 11/Dec/12 ] |
|
Closed, all commits on this ticket was reverted. |