-
Notifications
You must be signed in to change notification settings - Fork 77
Description
Feature Description
Currently, the "Modified" column in the Orders/Payments table displays the last modification time for each payment record but lacks sorting capability. This feature request adds sorting functionality to the Modified column, allowing users to sort payments by their last modification timestamp in ascending or descending order.
In my use-case, merchants need to quickly identify recently modified payments for auditing purposes, tracking changes, or investigating recent updates to payment records. Without sorting on the Modified column, users must manually scan through the list or rely on other filtering mechanisms, which is inefficient when dealing with large volumes of payment data.
Possible Implementation
The implementation involves:
- Enable Sorting Parameter: Add the
~showSort=trueparameter to theModifiedcolumn header configuration inOrderEntity.res - Key Correction: Update the column key from
modified_attomodifiedfor consistency with the API response field naming - Backend Support: Ensure the backend API supports sorting by the
modifiedfield (this should already be available)
The change is minimal and follows the existing pattern used for other sortable columns like "Created". The table component already has the infrastructure to handle sorting, so this is primarily a configuration update.
This enables the table's built-in sorting mechanism to work with the Modified column, allowing users to click the column header to toggle between ascending and descending sort order.
Have you spent some time checking if this feature request has been raised before?
- I checked and didn't find a similar issue
Have you read the Contributing Guidelines?
- I have read the Contributing Guidelines
Are you willing to submit a PR?
- Yes (PR is already prepared)