-
-
Notifications
You must be signed in to change notification settings - Fork 18
Open
Description
Problem
The --limit option only fetches the first N items. Pagination via cursor (after/before) is not supported, preventing users from iterating through large datasets.
Current State
issues listonly accepts--limitparameter- GraphQL queries use only
firstargument - No
after,before, or cursor support - Users cannot access results beyond the limit
Expected State
Support cursor-based pagination following Linear GraphQL API specification:
--limitfor result count (usesfirst)--after <cursor>to fetch next page--before <cursor>to fetch previous page- Response should include
pageInfowithhasNextPage,hasPreviousPage, and edge cursors
Impact
- Users with >50 issues cannot browse beyond default/specified limit
- Automation scripts cannot reliably paginate through results
- API inconsistency vs. Linear GraphQL capabilities
Technical Notes
- Requires updates to GraphQL queries to include
after,beforeparameters andpageInfofields - Service layer needs to accept and pass pagination parameters
- CLI commands need new options for
--afterand--before
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels