#mr_pablo

1 messages · Page 1 of 1 (latest)

floral minnow
#

I believe that's accurate as has_more maps to more data after that set, not before it

dire phoenix
#

but if you load the first page, without endingBefore, has_more is true

floral minnow
#

Exactly, because there's a 2nd page

dire phoenix
#

and there is still a second page when i view the first with endingBefore

#

it didn't disappear

floral minnow
#

I'm confused, can you provide req_xxx IDs and some JSON

dire phoenix
#

I'm doing this through a proxy API, and tracking the has_more value in our logs. But I can provide a customer ID for you to look up the session list

floral minnow
#

I just quickly tested this, and its working as expected IMO

dire phoenix
#

So you think that going from page 2 to 1, using the provided pagination params, has_more should be set to false ?

floral minnow
#

If page 2 is the last page, there are no more records

dire phoenix
#

but I'm going from page 2, to page 1, setting endingBefore as the first ID in the page 2 list

#

So im talking about being on page 1

#

I started on page 1, has_more is true. I go to page 2, using startingAfter and the last ID on page 1. I'm now on page 2.

#

Taking the ID of the first item on page 2, I make a URL, using endingBefore and the ID, this is taking me back to page 1. I'm now on page 1, and has_more is false

floral minnow
#

Ok, thanks for clear reproduction steps! I can see that now too

#

I'm still unsure if that is expected or not though (pagination is confusing)

#

I'll file an issue with the team

dire phoenix
#

TBH, the pagination on that endpoint is pretty poor, and this bug certainly doesn't help matters

wicked igloo
#

Thanks for feedback. We will forward to the team