Implement Pagination for Asset Retrieval #66
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.
Summary:
This PR introduces pagination to the asset retrieval functionality in our system. It modifies the
AssetRepo
to include aGetPaginated
method, allowing the API to fetch assets in a paginated format. This enhancement aims to improve performance and usability, especially when dealing with a large number of assets.Key Changes:
Pagination in Asset Retrieval:
GetPaginated
method toAssetRepo
which fetches assets based on the provided page number and limit per page.LIMIT
andOFFSET
clauses in the query to facilitate pagination.offset
based on the current page number and the number of records per page.API Endpoint Adjustment:
/assets
endpoint to support pagination parameters:page
andlimit
.Error Handling and Edge Cases: