sv::payload attribute

Use sv::payload to specify if the SubMsg::payload (opens in a new tab) should be forwarded as Binary. Exactly ONE reply method parameter can be marked with the sv::payload attribute. If missing, Sylvia will deserialize the payload to types defined after the sv::data parameter.

💡

To use sv::payload attribute pre Sylvia 2.0.0, you need to enable the replies feature using the sv::features.

Macros

List of macros supporting the sv::data attribute:

Usage

#[cw_serde]
pub struct ReplyPayload {
    pub receiver: Addr,
    pub coins: Coin,
}
 
pub struct Contract;
 
#[cfg_attr(feature = "library", sylvia::entry_points)]
#[contract]
#[sv::features(replies)]
impl Contract {
    pub const fn new() -> Self {
        Self
    }
 
    #[sv::msg(instantiate)]
    fn instantiate(&self, ctx: InstantiateCtx) -> StdResult<Response> {
        Ok(Response::new())
    }
 
    #[sv::msg(reply, reply_on=success)]
    fn success_handler(
        &self,
        ctx: ReplyCtx,
        #[sv::payload(raw)] payload: Binary,
    ) -> StdResult<Response> {
        Ok(Response::new())
    }
 
    #[sv::msg(reply, reply_on=error)]
    fn error_handler(
        &self,
        ctx: ReplyCtx,
        error: String,
        payload: ReplyPayload,
    ) -> StdResult<Response> {
        Ok(Response::new())
    }
 
    #[sv::msg(reply, reply_on=always)]
    fn always_handler(
        &self,
        ctx: ReplyCtx,
        result: SubMsgResult,
        receiver: Addr,
        coins: Coin,
    ) -> StdResult<Response> {
        Ok(Response::new())
    }
}

Sylvia uses the from_json (opens in a new tab) to deserialize the payload field, so it has to be serialized do JSON.

Override_entry_point Generated types