Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
betegon
force-pushed
the
bt/api-pagination-cursor
branch
from
October 26, 2026 15:16
b4cb377 to
4fe80fe
Compare
BYK
requested changes
Oct 26, 2026
BYK
left a comment
Member
There was a problem hiding this comment.
This should use the common pagination system in the repo now. We even have some custom cursors now. I'm surprised the lint rule did not catch this.
Otherwise, great change thanks a lot!
Member
|
I'd even argue we should let omitting the endpoint and other args or something so one can do |
This branch was previously deployed
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.
sentry api --jsondiscarded pagination metadata, leaving agents without a way to continue a successful query. It now exposes continuation metadata and uses the CLI's shared pagination history and custom cursor decoding, sonext,prev, andfirstwork consistently with native list commands.Before
Even when another page existed, the output had no continuation (bodies abbreviated):
{"status":200,"statusText":"OK","body":[{"slug":"example-org"}]}After
The same command includes navigation metadata:
{"status":200,"statusText":"OK","body":[{"slug":"example-org"}],"pagination":{"nextCursor":"1:1:0","hasPrev":false}}Repeat the endpoint and filters to navigate:
Raw cursors and custom bookmarks from the shared paginator are also accepted, including legacy
cli1~bookmarks. Resuming restores the cursor's required page size and skips rows already read; going forward and back retains that exact bookmark. This works for arrays and Events{data, meta}envelopes while preserving envelope metadata.Each invocation still fetches one server page, and the endpoint remains required. History is scoped to the request and identity; dry-runs and failed requests do not advance it.
hasPrevdescribes local navigation, whileprevCursoris server-provided.--fieldsfilters only the body, and raw/binary output stays unchanged. URL fragments are excluded without losing encoded#characters. Command help, docs, and the generated skill reference are updated.Continuing without an endpoint and native logs pagination remain separate follow-ups.
Validation