nspcc-dev / nspcc-dev/neofs-api
Reverse parameter to the Search API
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 11
- Forks
- 15
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 9
Description
Is your feature request related to a problem? Please describe.
Sometimes in UI, I would like to move backwards in the objects list. But using the current Search API (cursor), I can move only forward
Describe the solution you'd like
Append a Reverse parameter to the Search API. It will help to use the same cursor as a starting point, but move backwards.
Another thought to consider. If we pass an empty cursor and Reverse=true, could we return the last Count elements? It would help us to get the last page
Additional context
A user can start from a random place, having the cursor value copied from the browser address, during listing the object in UI.
Then, when it is used as a direct link, we show the next objects from the Cursor position, but can't go back with this list
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Search API declaration in the repository's proto files and reviewing how Cursor and Count are defined. Clarify the reverse traversal semantics, including whether an empty cursor with Reverse=true returns the last Count elements. Done means the API contract specifies and supports reverse pagination consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100