mirror of
https://github.com/nspcc-dev/neofs-node.git
synced 2026-03-01 04:29:10 +00:00
We need to make the change API process more clear for changing tests. #792
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#792
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 @anikeev-yadro on GitHub (Oct 11, 2022).
After API was changed we had output json changed too, as result our tests which use parsing output json had broken.
For example:
the old output was:
the new output is:
@cthulhu-rider commented on GitHub (Oct 11, 2022):
From one side, we do not guarantee backward compatibility in JSON format. From the other side, I think we need to improve JSON UX in tools like NeoFS CLI.
Possible solutions:
0. do nothing and leave it to the user's attention to protocol changes
a) beautifies some fields, e.g. IDs can be string-encoded instead of raw protobuf format
b) covers breaking cases like the mentioned one
@roman-khimov commented on GitHub (Dec 21, 2023):
JSON can be more stable than regular strings, but it needs to be controlled for that of course.