Feature: Adds ascending/descending sort toggle to Resource Manager#6531
Merged
donker merged 3 commits intodnnsoftware:developfrom May 1, 2025
Merged
Conversation
Contributor
Author
|
@microsoft-github-policy-service agree company="Trilogy" |
valadas
approved these changes
Apr 30, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements #5430 on 9.13.x
Summary
While allowing the user to sort files by name, date and size, the current implementation of the Resource Manager core module does not allow choosing the sort order (ascending/descending). This implementation adds this functionality.
Changes made
API
Current: The logic for sorting files in ascending/descending order is already implemented in
AssetManager.Instance.GetFolderContent(...), but the chain of calls from the endpointGetFolderContentto the classItemsManagerhas no option to change the default ascending order.Change: Logic for forwarding and taking into consideration the optional HTTP GET argument "sortingOrder" is implemented. Ascending order is used by default (i.e., when argument is not provided).
Frontend
Current: There is no toggle button for ascending/descending order.
Change: Added the toggle button, state for controlling the selected order, and adjusted existing calls to the API to always include the argument sortingOrder to persist the selected order.
Resources
Added words "Ascending" and "Descending" to the localization texts so that the respective state name is show when cursor moves over the added button.
Result