We discovered while working on search we discovered there are two types of paginated responses. One is when you know the total number of results ahead of time, and the other is when you don't. Prior to this change the ListResponse had two fields, one for each of these cases.
We realized it doesn't make sense to cover both situations in one struct so now this has been split into ListResponse for responses return a total number of results, and a StreamResponse, for responses with a currently unknown or unbounded total.
I have already tested the impact of this change on the Sourcegraph repo locally and once everything was converted to the right type of struct it worked well.
We discovered while working on search we discovered there are two types of paginated responses. One is when you know the total number of results ahead of time, and the other is when you don't. Prior to this change the ListResponse had two fields, one for each of these cases.
We realized it doesn't make sense to cover both situations in one struct so now this has been split into
ListResponse
for responses return a total number of results, and aStreamResponse
, for responses with a currently unknown or unbounded total.I have already tested the impact of this change on the Sourcegraph repo locally and once everything was converted to the right type of struct it worked well.
@shurcooL