Currently when a websocket authentication fails, there is no indication of this to the end-user, and the websocket connection will stay alive despite not receiving anything from the server. Instead, the websocket should throw an error when authentication fails. This would mean that Shard#launch() would now be error-prone, I'm not sure if that should be considered a breaking change.
Currently when a websocket authentication fails, there is no indication of this to the end-user, and the websocket connection will stay alive despite not receiving anything from the server. Instead, the websocket should throw an error when authentication fails. This would mean that
Shard#launch()would now be error-prone, I'm not sure if that should be considered a breaking change.