Feat: Paginate getIssues() to fetch all issues#6
Open
mojek wants to merge 1 commit intocasals:masterfrom
Open
Conversation
Previously getIssues() was hardcoded to fetch only the first 100 issues with no pagination support. Workspaces with more than 100 issues would silently miss data during sync. Added cursor-based pagination using Linear API's pageInfo connection pattern (hasNextPage + endCursor) to iterate through all pages. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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 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.
Summary
getIssues()was hardcoded tofirst: 100with no pagination — workspaces with >100 issues silently missed data during syncpageInfo { hasNextPage, endCursor }connection patternhasNextPageis false, accumulating resultsTest plan
updatedAfterfilter) still works correctlygetIssues: fetched X issues total