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
It would be great if we could generate a "raw" message composer as well, or have an optional parameter to the message composer so that we can build the "raw" messages like this:
{
install_module: {init_msg: initMsg,module,
}
instead of the MsgExecuteContractEncodeObject (which you need to deconstruct to msg.value.msg otherwise).
The code would probably look like the following:
installModule=({
initMsg,
module,}: {initMsg?: Binarymodule: ModuleInfo},// this return typing below does not exist yet but would be really nice!): InstallModuleExecMsg=>({install_module: {init_msg: initMsg,
module,},})
It would be great if we could generate a "raw" message composer as well, or have an optional parameter to the message composer so that we can build the "raw" messages like this:
instead of the
MsgExecuteContractEncodeObject
(which you need to deconstruct tomsg.value.msg
otherwise).The code would probably look like the following:
(vs currently):
The text was updated successfully, but these errors were encountered: