I'm currently tasked with implementing client side sorting on specific page view for our application.
Below is an example of how the UI for client side sorting works, basically a user can click on a desired table header so results are sorted in ascending or descending order (using JavaScript). This example is static, but hopefully it conveys a clear idea of how the solution looks and functions.
name | progress ⬇︎ | created | accessed |
---|---|---|---|
Bob | 95% | 02/23/2021 | 05/02/2021 |
Alice | 45% | 04/12/2021 | 06/22/2021 |
John | 23% | 05/25/2021 | 03/12/2021 |
After working on the pull request, one of the developers pointed out that this feature seems unnecessary because the endpoint that brings in the results is paginated, and for this reason, it makes no sense to have client side sorting. The justification was that "It gives obviously false sorting because you don't sort the full dataset".
I thought about this and I'm inclined to disagree with that statement; as a user, it makes sense to have the ability to sort paginated results to find what you're looking for without having the entire set of results. Is my assessment correct?