nspcc-dev / nspcc-dev/neofs-node
Merge metabase struct field into interface in `Shard`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
what does not allow doing it now?
Originally posted by @carpawell in https://github.com/nspcc-dev/neofs-node/pull/3531#discussion_r2282784642
it would be possible to synthesize a metabase interface for the shard and use it throughout the code, but this would affect many elements. Therefore, it is postponed till this
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 the Shard and metabase definitions and the discussion linked from pull request #3531. Map how the metabase struct field is used throughout the code and identify the affected elements before proposing the interface change. Done means the metabase interface is synthesized for Shard and used consistently, but the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100