fix: follow pagination in Linear, Google Drive, Asana, and Shopify list ops#516
Merged
Conversation
Continues #455 (after Stripe/Slack in #496): the remaining list ops that fetched only the first page. - Linear issueSearch: follow the Relay pageInfo cursor (hasNextPage/endCursor). - Google Drive list: follow nextPageToken (added to the fields mask). - Asana projects/tasks: follow the next_page.offset token. Each collects up to the existing per-op limit (<=100) and is bounded by a hard page cap. Adds multi-page regression tests for all three. Advances #455 (Shopify Link-header, HubSpot, DynamoDB remain).
Shopify paginates list endpoints with an RFC-5988 Link header (<...?page_info=XYZ>; rel="next"); orders and products fetched only the first page. Add _next_page_url() to parse the rel="next" cursor and a _paginated_list() helper that follows it (the next-page URL already carries limit + page_info, so follow-up requests drop the other params). Bounded by the per-op limit and a hard page cap. Adds a Link-header multi-page regression test. Advances #455 (HubSpot and DynamoDB remain).
cdayAI
changed the title
2 tasks
This was referenced Jun 1, 2026
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
2 participants
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.
Continues #455 (the connector-pagination catch-all). After Stripe/Slack landed in #496, this covers the next batch of first-page-only list ops.
issueSearchpageInfo { hasNextPage endCursor }cursorlistnextPageToken(added to thefieldsmask)projects,tasksnext_page.offsettokenorders,productsLink: rel="next"header (page_infocursor)Each loop collects up to the existing per-op limit and is bounded by a hard page cap, so a huge collection can't spin unbounded.
Verification
Multi-page regression tests added for all four (each asserts the 2nd request carries the cursor/token/offset/Link-URL from the 1st response). Relevant batches green;
ruff checkand theshell=Truelint guard clean.Remaining in #455
HubSpot (
paging.next.after) and DynamoDB (LastEvaluatedKey) — same shape, left for a follow-up; tracked in #455.🤖 Generated with Claude Code