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
MsgCreateClient contains a field with type Header which contains an embedded SignedHeader along with a "validator_set". However the embedded field is not unrolled so the resulting JSON has a field called "SignedHeader". Presumably we want the SignedHeader to be unrolled so that each of "header", "commit, and "validator_set" are at the same level, or at least for it to be proper snake_case. Adding a JSON dump to the test gives:
We might want to build something that dumps all the msg types to JSON and runs some simple lints on it to prevent this in the future. Also we might want to double check them by eye just to make sure it all looks good.
This isn't a big deal in practice (not a bug per se), but we should try to be consistent and sensible with the JSON types which will help the overall UX and implementing in other langs.
Maybe this all goes away with proto, not sure. In any case, we might still want to have that JSON dumping tool so we can still sanity check everything.
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Summary of Bug
MsgCreateClient contains a field with type Header which contains an embedded SignedHeader along with a
"validator_set"
. However the embedded field is not unrolled so the resulting JSON has a field called"SignedHeader"
. Presumably we want the SignedHeader to be unrolled so that each of"header"
,"commit
, and"validator_set"
are at the same level, or at least for it to be proper snake_case. Adding a JSON dump to the test gives:Version
ibc-alpha branch b85f82e
Steps to Reproduce
JSON dump the MsgCreateClient
We might want to build something that dumps all the msg types to JSON and runs some simple lints on it to prevent this in the future. Also we might want to double check them by eye just to make sure it all looks good.
This isn't a big deal in practice (not a bug per se), but we should try to be consistent and sensible with the JSON types which will help the overall UX and implementing in other langs.
Maybe this all goes away with proto, not sure. In any case, we might still want to have that JSON dumping tool so we can still sanity check everything.
For Admin Use
The text was updated successfully, but these errors were encountered: