Adding API pagination to the Dashboard Order Lists #681 #873
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.
Pull Requests Requirements
Summary
Added API pagination logic into Orders controller & Integrated Home Dashboard with API pagination functionality.
Before, all the data would go to the Frontend and would be paginated there only, now the data gets paginated by the API(100 results per bundle) and is sent in chunks/bundles to the Frontend for further pagination by the Frontend(i.e into 10, 20, 30, 50 or 100 results per page).
Video
Before
Recording.2024-03-23.132316.mp4
After
To test the pagination, property
org.openelisglobal.paging.results.pageSize:2
was set to 2(i.e. 3 results per page), this test is shown below along with enabled/disabled Next and Previous Bundle buttons.Recording.2024-03-23.133351.mp4
Related Issue
Issue - #681
https://github.com/orgs/I-TECH-UW/projects/6/views/1?pane=issue&itemId=49773666