nspcc-dev / nspcc-dev/neofs-node
Add functional address handler for `engine.ListWithCursorPrm`
Open
Nobody has claimed this yet.
enhancement
good first issue
I4
neofs-storage
S3
U4
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
Is your feature request related to a problem? Please describe.
I'm always frustrated when we can't handle the addresses of objects from engine.ListWithCursorPrm without using an intermediate memory buffer.
Describe the solution you'd like
New function with functional handler for the addresses of objects in list.
Additional context
Idea of this come from this pr #2933.
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 inspecting the engine.ListWithCursorPrm entry point and the approach discussed in PR #2933. Trace how object addresses are currently returned, then define the new functional handler so callers can process those addresses without an intermediate memory buffer; done means the handler is available and covered by the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100