Runtime Error Should Have an Error Code

[jmakar-boom]

Version affected
0.1.31

Describe the bug
I have a multi-source stream to which nothing is being broadcast. A client attempts to connect to listen for broadcast events. The client receives a runtime error with no useable error code. As this is a predictable error I would expect some kind fo error code for handling in the client. It results in a 400 HTTP status error saying 'stream not being published'.

To Reproduce
Steps to reproduce the behavior:
Run this code snippet with an initialized millicastView instance.

//Start connection to publisher
try {
    await millicastView.connect({
        events: ["active", "inactive", "vad", "layers"]
    })
    
} catch (e) {
    console.log("error", e);
}

Expected behavior
I would expect an error code for handling the client behavior. To be honest, I personally would prefer no error and allow it to sit there and listen for broadcast events anyway. But if it must fail, I would like a handleable error code.

Screenshots

Environment (please complete the following information):
n/a

Additional context
Multi-source stream, if that matters

[nico-ramos]

Hi, we're going to work on that in the future, for now you should handle the different errors by it's message.
I can't give you an estimate of when it will be done since it's going to be mainly a server-side fix.
Thanks