Given I make the following calls:
/transactions?blockId=:blockId&sort=timestamp:desc&offset=0&limit=51 and
/transactions?blockId=:blockId&sort=timestamp:desc&offset=50&limit=51
I expect the last item returned by the first call to be the same as the first item returned by the second call.
It is not.
Using the following test database:
Compare the first call with the second call
v1.0.0-beta.5
Your calls are getting transactions with timestamp 0. What we need is a second default sort parameter as a tiebreaker.
Maybe it's a good idea to introduce this second default sort for all endpoints that have sorting option.
Most helpful comment
Maybe it's a good idea to introduce this second default
sortfor all endpoints that have sorting option.