mirror of
https://github.com/nspcc-dev/neofs-node.git
synced 2026-03-01 04:29:10 +00:00
Renaming time #1172
Labels
No labels
I1
I2
I3
I4
S0
S1
S2
S3
S4
U0
U1
U2
U3
U4
blocked
bug
config
dependencies
discussion
documentation
enhancement
enhancement
epic
feature
go
good first issue
help wanted
neofs-adm
neofs-cli
neofs-cli
neofs-cli
neofs-ir
neofs-lens
neofs-storage
neofs-storage
performance
question
security
task
test
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neofs-node#1172
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @carpawell on GitHub (Dec 21, 2023).
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 chainDescribe alternatives you've considered
Do nothing cause we may break something.
@roman-khimov commented on GitHub (Dec 21, 2023):
These are very different things. node->storage is mostly blocked by potential compatibility issues.
morphclient isn't really needed. fs chain can be renamed right away.@carpawell commented on GitHub (Dec 21, 2023):
Do you know what is it?
"sidechain" wording used in logs. Why is it better to do this than binary renaming? Both are smth that can be used by a user. Well, binary is more probable but still.