Allow for /next/n to be inclusive

Question

Allow for /next/n to be inclusive

Closed this issue 7 years ago · 5 comments

lucasmo commented 7 years ago

We have a pattern where, given a hub uri, we want to get the next n items inclusive of the given hub uri.

Something like:
/channel/foo/2017/11/17/00/00/00/000/abcdef/next/1000?inclusive=true&bulk=true

Answer 1 · 2017-12-01T18:34:25.000Z

@lucasmo are there any other endpoints where this is needed? What about earliest & latest?

Answer 2 · 2017-12-01T18:36:25.000Z

@lucasmo if you query /next/1000 with inclusive, do you expect 1001 items?

Answer 3 · 2017-12-01T18:50:30.000Z

I can see potentially doing the same for "previous" but not "earliest" or "latest" personally. I think we would be tolerant of N or N+1 items, though I would expect N based on the request.

Answer 4 · 2017-12-04T22:07:59.000Z

I agree with what Zack said.

Answer 5 · 2017-12-05T17:40:35.000Z

Excellent.
We will add inclusive to next and previous, and we will return the number of items requested.