filtering, sorting and pagination
As my task app is getting more complex, I need to add the ability for users to filter and sort. I want to also be able to create persistent views for the user. Since the number of tasks is large, in order to have a good UX and low latency, I also need pagination. Currently, task interactions like status changes, due date changes, etc. are all optimistically updated and it is a great UX that I wish to preserve.
Q1) Given there is a requirement for pagination, 1) filtering and 2) sorting will need to be implemented on the server right?
Q2) Assuming (1) is a yes, how should this be implemented exactly? Any examples of what these parameters for filters and sorts should look like would be super helpful. I don't want to reinvent the wheel.
Q3) In order to implement views, these params would need to be stored on the backend. Any resources on the best practices here?
Q4) Optimistic updates with filters and sorts applied - should be I be filtering and sorting locally for the tasks from the page I am on?
1 Reply
national-gold•2y ago
Q4) +1