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
After upgrading to v0.50.x, queries that were migrated to autocli now use different aminojson for encoding responses. This now makes the queries harder to read because they show values instead of the string name.
Cosmos SDK Version
v0.50.3
How to reproduce?
Launch network, create any proposal, do <app> query proposal 1, look at the status field. It is now a number, but in v0.47.x it was a string such as STATUS_PASSED.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
What happened?
After upgrading to v0.50.x, queries that were migrated to autocli now use different aminojson for encoding responses. This now makes the queries harder to read because they show values instead of the string name.
Cosmos SDK Version
v0.50.3
How to reproduce?
Launch network, create any proposal, do
<app> query proposal 1
, look at the status field. It is now a number, but in v0.47.x it was a string such asSTATUS_PASSED
.The text was updated successfully, but these errors were encountered: