nspcc-dev / nspcc-dev/neofs-api
Describe size limitations
Open
Nobody has claimed this yet.
documentation
enhancement
I3
S4
U4
- Dominant language
- Makefile
- Stars
- 11
- Forks
- 15
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 9
Description
There is no clear statement on the maximal sizes of object header, attribute, eACL records, etc. It may be important for different language implementations.
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
Review the repository's API documentation and proto files declarations, focusing on object headers, attributes, and eACL records. Determine the maximal sizes that apply to each record and document them clearly for different language implementations. Done means the relevant size limitations are stated in the project documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100