Repository navigation
feat: add pagination support to list commands - #72
Merged
Merged
Conversation
Add pagination support to objects list, buckets list, access-keys list, and iam policies list. When flags are used, JSON output wraps items with a paginationToken field; table output prints a next-page hint to stderr. Without flags, behavior is unchanged (backwards compatible). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 49e66c4. Configure here.
Commander.js passes CLI options as strings. The generic getOption<number> is only a type assertion, not a runtime conversion, so limit was passed as "10" (string) to SDK methods expecting a number. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
MantasMiksys
approved these changes
Apr 8, 2026
Contributor
|
🎉 This PR is included in version 2.16.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
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
--limitand--page-tokenflags toobjects list,buckets list,access-keys list, andiam policies listpaginationTokenfield, table output prints a next-page hint to stderr, XML adds a<paginationToken>elementTest plan
npm run buildcompiles cleanlynpm test— all 541 tests pass (includes new tests forgetPaginationOptionsandformatPaginatedOutput)tigris objects list <bucket> --limit 2returns 2 items + token hint in stderrtigris buckets list --limit 5 --jsonreturns wrapped JSON with pagination tokentigris buckets list(no flags) — unchanged output🤖 Generated with Claude Code
Note
Medium Risk
Adds new CLI flags and alters output shape when pagination is enabled (notably JSON wrapping and new stderr hints), which could affect automation that opts into pagination. Also bumps
@tigrisdata/storage, introducing some dependency-level behavior change risk.Overview
Adds opt-in pagination to
buckets list,objects list,access-keys list, andiam policies listvia new--limit/--page-tokenflags, passing these through to the underlying IAM/storage SDK calls.Introduces
formatPaginatedOutput(JSON wraps{ items, paginationToken? }, XML appends<paginationToken>, tables remain the same) plus aprintPaginationHintstderr hint for fetching the next page; updates command specs to document the new flags and adds unit tests for the new formatting/options helpers. Also bumps@tigrisdata/storageto^2.16.2(and lockfile deps updated accordingly).Reviewed by Cursor Bugbot for commit 1d17904. Bugbot is set up for automated code reviews on this repo. Configure here.