feat : implement pagination to get-all-waitlist #1303
Merged
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 Request
Description
This PR adds pagination support to the
getAllWaitlist
endpoint in the Waitlist module. The changes include modifying theWaitlistService.getAllWaitlist
method to accept optionalpage
andlimit
query parameters, using these values to calculateskip
andtake
for the TypeORM query, and returning a uniform API response that includes pagination details (current page, total pages, total waitlist count, and waitlist entries). Additionally, the Swagger documentation has been updated to reflect these changes, and the test suite has been updated to validate the new pagination behavior.Related Issue
Fixes #1233
Type of Change
How Has This Been Tested?
Test Evidence
Screenshots (if applicable)
Documentation Screenshots (if applicable)
Checklist
Additional Notes
This PR refactors the
getAllWaitlist
method to improve performance and scalability by reducing the amount of data retrieved from the database.