Add paging and sorting functionality to find all/search functionality

[jackcmeyer]

🚀 Feature Proposal

Add paging and sorting functionality to the search/find all functions for patients, appointments, lab.

Motivation

• Patient Search/List, Appointment List, Lab List

[akshay-ap]

Can I take this one?

[jackcmeyer]

Sounds good @akshay-ap.

i've already done sorting for the findAll, however, we need to implement it for search yet.

For this, I'm hoping we can end up with:

search(searchCriteria: SearchCriteria, sort?: SortRequest, page?: PageRequest)

and

findAll(sort?: SortRequest, page?: PageRequest)

if a page request is provided, it should return a Page<T> of whatever. Page should look like:

class Page {
	T[] content;
	size: number; // the size of the page
	number: number; // the page number of the returned page
    totalElements: number; // the total elements that would be returned by query
    totalPages: number; // total number of pages that would be for this query
	getNextPage(): Page<T>
    getPreviousPage(): Page<T>
    hasNextPage: boolean
    hasPreviousPage: boolean
}

Page request should look like:

interface PageRequest {
  number: number; // requested page number
  size: number; // requested size of the pages
}

sort and page should always be optional and if they are not provided then we should default to Unsorted and Unpaged.

paging and sorting should always be done at the PouchDB level

we should be able to support getting a specific page and getting the next and previous page.

[akshay-ap]

@jackcmeyer Thanks for the pointers!

[jackcmeyer]

@akshay-ap No worries, please let me know if you have any questions. I've done a little bit of research into this.