Closed
Description
Summary
The mapping from cosmwasm data to the query output is not so clean. We often use string to represent data we know is either (1) binary or (2) json. Let us use []byte
/tmbytes.HexBytes
for the binary data and json.RawMessage
for the json.
Problem Definition
wasmcli query wasm
output is often hard to read
Proposal
ContractInfo
should havejson.RawMessage
([]byte
alias) forInitMsg
types.Model
used byQueryMethodContractStateAll
andQueryMethodContractStateRaw
should not be{string, string}
, but{HexBytes, json.RawMessage}
For Admin Use
- Not duplicate issue
- Appropriate labels applied
- Appropriate contributors tagged
- Contributor assigned/self-assigned
Metadata
Metadata
Assignees
Labels
No labels