Websocket type activeAssetCtx can return wrong channel type activeSpotAssetCtx

[syahrul12345]

When subscribing for asset contexts, but the coin is a spot market:

{"method":"subscribe","subscription":{"type":"activeAssetCtx","coin":"@107"}}

The return value has a different channel type of activeSpotAssetCtx
The example payload is this:

{
    "channel": "activeSpotAssetCtx",
    "data": {
        "coin": "@107",
        "ctx": {
            "prevDayPx": "23.993",
            "dayNtlVlm": "228614808.04913011",
            "markPx": "23.277",
            "midPx": "23.281",
            "circulatingSupply": "334395529.28086698",
            "coin": "@107",
            "totalSupply": "999840322.48575342",
            "dayBaseVlm": "9756716.93999999"
        }
    }
}

The rust sdk is unable to handle this case. I will create a PR to handle this if this is indeed a bug

[syahrul12345]

let (sender, mut receiver) = unbounded_channel();
    info_client
        .subscribe(
            Subscription::ActiveAssetCtx {
                coin: "@107".to_string(),
            },
            sender,
        )
        .await
        .unwrap();
    tokio::spawn(async move {
        while let Some(msg) = receiver.recv().await {
            //Never enters
            println!("Received active asset ctx: {:?}", msg);
        }
    });

The problem lies with the mismatch between type and channel, when the subscription is first created, activeAssetCtx is used as an identifier, but after receiving the response from the websocket endpoint, because channel is of activeSpotAssetCtx, it uses this as an identifier, which doesnt exist when the subscription was first created

[namn-grg]

Hey @syahrul12345 yes seems this is bug, pls make a PR with fix if you want :)

[syahrul12345]

alright, probably will create this tomorrow morning