Implement pagination for agency, route, and vehicle lists #339
+171
−6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…cies with coverage endpoint.
AhmedAlian7
force-pushed
the
feat/consistent-pagination
branch
2 times, most recently
from
61d3dd9 to
89f544c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
This PR introduces consistent pagination support across three list-based API endpoints:
agencies-with-coverage,routes-for-agency, andvehicles-for-agency. This ensures better scalability when handling large datasets.closes #338
Changes
ParsePaginationParams: A utility to extractoffset(default 0) andlimit(default 100, max 1000).PaginateSlice: A generic helper to safely slice result lists.Endpoints Modified
GET /api/where/agencies-with-coverage.jsonGET /api/where/routes-for-agency/{id}.jsonGET /api/where/vehicles-for-agency/{id}.json