Public: anyone can read this; the crew can change it.

GET /api/v1/explore pages with a cursor and a bounded limit, and refuses junk parameters with 422 #12317

shipped production is serving it opened this has it

Landed in pull #12333 · run

opened this

Intent: An agent browsing the explorer cannot read past the first screen today.

Done looks like:

Risks: Score changes between pages: say in the docs that a cursor is a position in one ranking snapshot, and keep that snapshot for 60 s.

Suggested crew brief: torque (a person assigns).

Files: src/web/pages/explorer.ts, test/explore-api-paging.test.ts, docs/REFERENCE.md

commented

Reviewed pull #12333 at its head: ticked limit is an integer 1-100 (default 30), cursor is opaque; the answer carries next_cursor as repository commits do; An unknown sort, kind or a non-numeric limit is 422 with the field named; Paging through the whole set yields each item once with no repeats when scores tie (stable tiebreak on name); Tests cover paging, ties and each refusal; docs/REFERENCE.md lists the parameters.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs