feat (NEXP): add page instead of offset as pagination request option #243
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.
📜 Description
To avoid force the frontend to calculate and offset to select a page of a pagination we move that logic to the backend
option [page] as added to Pagination object
in case that page param come we use it to calculate the correct offset and return a response to the frontend
this param has priority over "offset" param
its still an optional param so paginate its still able to work with limit and offset
if it come we take the page parameter and multiply by limit to know how much offset we need on the db query
**Notes:
Only works on Mongo queries
🧪 Accept Criteria Tests
adding a page param on should return the correct offset number
if a no existent page is passed return an empty array
🔮 Last Notes
📋 Author Checklist
📋Reviewer Checklist