-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Serde Feature #22
Add Serde Feature #22
Conversation
f09be04
to
e34731a
Compare
It should be noted that the decision was made in this PR to consistently use base58 encoding for all keys and key-related types as the way serde handles these datatypes. This includes secret keys and signatures. This also means that we aim to apply the same encoding rule to serde features of phoenix keys and their respective types, unless they are already defined to be encoded in a different format. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks good in general, but having tests for all serde implementations is desirable.
9b8d533
to
ed52ff1
Compare
0b2cd29
to
393ade1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice if the tests would also run by default or in the CI. Currently they are feature gated, so cargo test won't let them run by default
Can you add the test with the serde feature to the CI as well?
028d3cd
to
a28a10f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM from my side
a28a10f
to
6362a7d
Compare
Serialize
and Deserialize
for execution-core
For dusk-network/rusk#2773 and #21.