You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While both formats can be casted to each other, it's not really convenient to compare the values visually. I propose to work out for this case and others like it a string format at the convention level. Why conventions? For example, for object/container IDs, a string format is declared at the protocol level.
To conveniently follow the convention, it is proposed to create a special function in the SDK, which will be used whenever it is required to comply with the generally accepted format.
Currently we print storage node ID (which is actually its public key) in different formats. For example:
neofs-node/pkg/innerring/processors/netmap/process_peers.go
Lines 60 to 66 in cd71de6
neofs-node/cmd/neofs-cli/modules/control/snapshot.go
Lines 64 to 65 in cd71de6
While both formats can be casted to each other, it's not really convenient to compare the values visually. I propose to work out for this case and others like it a string format at the convention level. Why conventions? For example, for object/container IDs, a string format is declared at the protocol level.
To conveniently follow the convention, it is proposed to create a special function in the SDK, which will be used whenever it is required to comply with the generally accepted format.
Btw which format do you prefer? For me its hex 🐑. @fyrchik @carpawell
The text was updated successfully, but these errors were encountered: