nspcc-dev / nspcc-dev/neofs-node
Renaming time
Open
Nobody has claimed this yet.
discussion
documentation
I3
S2
U3
- 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 i see the same thing named two different ways.
Describe the solution you'd like
neofs-node->neofs-storageeverywheremorphclient -> ???sidechain/morph->neofs chain
Describe alternatives you've considered
Do nothing cause we may break something.
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
No files, tests, or entry points are named. Search the repository for neofs-node, morph, and sidechain to map the affected references and determine the complete rename scope; done means the terminology is consistent everywhere without breaking existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- developer-experience
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100