Open
Description
Current Behavior
prev_page is always null.
Expected Behavior
It should return the seek for the previous page if there is one.
Steps To Reproduce
You can see the issue on docs.rs:
Go to https://docs.rs/releases/search?query=sysinfo
Click "next page"
Then you can see that there is no "previous page" button. I originally suspected a bug on docs.rs side but after investigating, it looks like the ["api", "v1", "crates"] query always return a null prev_page in the JSON response.
Environment
No response
Anything else?
No response
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Participants
Activity
Turbo87 commentedon Jan 8, 2025
That's intended behavior. The way seek pagination is implemented we can't offer reverse traversal without sacrificing performance.
GuillaumeGomez commentedon Jan 8, 2025
I see. I suppose we can store the previous page in the cookie session... Gonna find something out.
eth3lbert commentedon Jan 9, 2025
I don't expect significant performance issues. It would only involve some reverse handling (including query and result processing). This is actually one of the enhancement items on my backlog.