While working on Explorer and using Iroha crates as libraries, found a few minor yet hardly workaroundable issues. Some of them related to not using iroha_data_model with transparent_api feature, which revealed some inconsistencies with data access.
Solution
Expose getters for the following structs: BlockSignature, TransactionSignature, NumericSpec
iroha_crypto::Signature: make serialization transparent instead of { "payload": "..." }. This field is redundant and inconsistent with other iroha_crypto structures - they all serialize as plain strings.
Migration Guide (optional)
If you passed Signature in JSON, do not nest it into an object with payload field anymore.
Context
While working on Explorer and using Iroha crates as libraries, found a few minor yet hardly workaroundable issues. Some of them related to not using
iroha_data_model
withtransparent_api
feature, which revealed some inconsistencies with data access.Solution
BlockSignature
,TransactionSignature
,NumericSpec
iroha_crypto::Signature
: make serialization transparent instead of{ "payload": "..." }
. This field is redundant and inconsistent with otheriroha_crypto
structures - they all serialize as plain strings.Migration Guide (optional)
If you passed
Signature
in JSON, do not nest it into an object withpayload
field anymore.Checklist
CONTRIBUTING.md
.