[MGNLUI-3814] Allow configuration of defaultOrder in grids: descending or ascending Created: 16/Mar/16 Updated: 22/Jun/21 Resolved: 09/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | content app |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.7 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Simon Aebli | Assignee: | Milan Divilek |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | VN-Testing, support, ux-improvement-selected | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||||||||||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||||||||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||||||||||||||||||||||||||
| Documentation update required: |
Yes
|
||||||||||||||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | UI framework implementation | ||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | UI FW 23 | ||||||||||||||||||||||||||||||||||||||||||||
| Story Points: | 3 | ||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
At the moment, we can define a default order for the subapps. Unfortunately, we can only specify the property name and not if the column should be ordered descending, which comes helpful e.g. for an app maintaining latest news. Customers can define sortable properties in the JcrDatasource with `sortByProperties`. Just not which direction. Notes: Maybe add a sortOrder configuration to BaseDatasourceDefinition which allows for ASC/DESC values. We would replace sortByProperties list with a map like firstProperty : asc; secondProperty : desc; ... We'll still support the list for compatibility as deprecated. The below was split into
|
| Comments |
| Comment by Christopher Zimmermann [ 17/Mar/16 ] |
|
renamed after discussing with partner. |
| Comment by Antti Hietala [ 15/Feb/17 ] |
|
Use cases:
These uses cases are not possible today because
|
| Comment by Richard Gange [ 05/May/20 ] |
|
mgeljic Can this ticket be closed since we have this configuration from BaseDatasourceDefinition? Seems like I can sort on property names when using JcrDatasourceDefinition. cc viet.nguyen |
| Comment by Mikaël Geljić [ 06/May/20 ] |
|
sorting direction is still relevant for superseding JCR datasource config |
| Comment by Richard Gange [ 04/Jan/21 ] |
|
The content connector configuration has been replaced by the datasource configuration. See https://docs.magnolia-cms.com/product-docs/Apps/App-configuration/Data-source-definition.html |
| Comment by Christopher Zimmermann [ 04/Jan/21 ] |
|
Does the datasource configuration or app configuration support supplying a default sort DIRECTION (ascending, decending?) If not the ticket shoud remain open. I don't see anything like that specified here: https://docs.magnolia-cms.com/product-docs/Apps/App-configuration/Data-source-definition/JCR-data-source.html |
| Comment by Christopher Zimmermann [ 25/Jan/21 ] |
|
Reopening this ticket, as the comments and links are still relevant and useful in understanding value of ticket. |