HELD until the API returns next_cursor on order flow: page order flow with --cursor - #6
Closed
0xFantomMenace wants to merge 1 commit into
Closed
0xFantomMenace wants to merge 1 commit into
0xFantomMenace wants to merge 1 commit into
Conversation
Restores the order-flow paging help and output for when the API returns next_cursor on order flow. Hold until then. - `--cursor` help: the previous response's cursor, sent with the same --start, --end and --interval. `--limit` counts buckets per page. - With --out, the summary reports has_more and nextCursor, and pretty output says when more data is available, as order history does. - README: how to page with --cursor. - CHANGELOG: order flow pages with nextCursor.
0xFantomMenace
force-pushed
the
docs/order-flow-paging
branch
from
September 29, 2026 02:09
f059dcc to
e7545f3
Compare
0xFantomMenace
force-pushed
the
master
branch
from
September 29, 2026 02:09
2084901 to
b53ed47
Compare
Member
Author
|
Included in #9 (order flow paging help and README). |
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
1 participant
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.
Held. Do not merge until the API returns
next_cursoron order flow. The API already buckets order flow at1m,5m,15mand1hand reads a sentcursor, but it does not returnnext_cursoron order flow yet. That arrives with an API switch, which is turned on after SDK releases that forward the cursor are published. Merge this once the switch is on and verified.#5, which keeps
--cursorand drops the paging help and output, is merged, and this PR now targetsmaster. Its diff is only the paging help and output.Changes
oxa orders flowandoxa hip4 orders flow:--cursorhelp says it is the previous response's cursor, sent with the same--start,--endand--interval;--limitcounts buckets per page (default 1000, max 10000).--out, the summary reportshas_moreandnextCursor, and pretty output shows "Has more" and says when more data is available, asoxa orders historydoes. (Before the API switch these would always read "no more", which is why they are held.)--cursorrow and how to page.Before merging
next_cursoron order flow: a full day at1mon BTC gives 1000 buckets plus a cursor, then the other 440.master(both done).Test plan
tsc --noEmit: clean.vitest run: 73 passed (5 files).