You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Improvement
It'd be nicer and more efficient if the server detected that it finished short of its limit (whether default or specified) and didn't send a next token when it can know that there's nothing after that next token.
In the current state, adding the next token to the query produces an empty result, which is a pretty clear sign of being done, but yeah it could be better.
curl localhost:8980/v2/accounts/XIU7HGGAJ3QOTATPDSIIHPFVKMICXKHMOR2FJKHTVLII4FAOA3CYZQDLG4/transactions?after-time=2020-06-03T10:00:00-05:00 | json_pp
The text was updated successfully, but these errors were encountered: