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
cw-controllers are using CosmosMsg<Empty> (and relatives) when it comes to messaging. This is an issue, as it makes them unusable in chains which have their specific custom message (and there is no way to simply map those). The solution is simple - as those utilities are never using Custom, instead of returning cosmwasm_std::Response, they should return generic cosmwasm_std::Response<T>, for eg the cw_controllers::Admin::execute_udpate_admin may look like:
cw-controllers
are usingCosmosMsg<Empty>
(and relatives) when it comes to messaging. This is an issue, as it makes them unusable in chains which have their specific custom message (and there is no way to simply map those). The solution is simple - as those utilities are never usingCustom
, instead of returningcosmwasm_std::Response
, they should return genericcosmwasm_std::Response<T>
, for eg thecw_controllers::Admin::execute_udpate_admin
may look like:C should be easy to infer, as those calls are used to directly return them.
The text was updated successfully, but these errors were encountered: