nspcc-dev / nspcc-dev/neofs-api
Status for already removed container
Open
Nobody has claimed this yet.
feature
I3
S3
U4
- 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.
Container contract supports the exception since https://github.com/nspcc-dev/neofs-contract/pull/404. Once container is removed, it becomes inoperable. This fact would be nice to be highlighted in responses
Describe the solution you'd like
add CONTAINER_ALREADY_REMOVED status
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 reading status/types.proto at the referenced lines in neofs-api and compare the existing removed-container status in neofs-contract. Add the requested CONTAINER_ALREADY_REMOVED status declaration where the API status values are defined, then verify the proto files remain valid and the new status is exposed in responses.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100