This repository was archived by the owner on Oct 16, 2025. It is now read-only.
fix: handle pagination for projects with >20 segments #23
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
- Add pagination loop to fetch all segments in chunks of 20 - Use offset and limit query parameters to iterate through pages - Prevent silent data loss when importing large segment sets - Continue fetching until totalCount is reached Fixes issue where only first 20 segments were imported from projects with more than 20 segments due to API pagination limits.
EladBet
force-pushed
the
fix/segment-pagination-limit
branch
from
e564f41 to
529e6fc
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes issue where only first 20 segments were imported from projects with more than 20 segments due to API pagination limits.