{{ message }}
This repository was archived by the owner on Aug 17, 2026. It is now read-only.
Feat/pagination helper - #78
Open
LifeJiggy wants to merge 1 commit into
Open
Conversation
Collaborator
Author
|
Thanks for the feedback, @bbatha! 🙌 |
LifeJiggy
force-pushed
the
feat/pagination-helper
branch
from
November 27, 2025 11:37
985ec36 to
e733095
Compare
Author
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 adds a PaginationHelper utility class that simplifies handling paginated API responses, enabling developers to easily fetch all items across multiple pages.
Problem
Many Gradient API endpoints return paginated results, requiring developers to manually handle pagination logic. This leads to:
Solution
Add PaginationHelper class with:
Key Features
Benefits
Testing
All tests pass with full coverage of pagination functionality.
Usage Examples